[IPython-user] Ipython autocompletion and enthought.mayavi
Thu May 28 17:30:11 CDT 2009
Same thing happens in my Fedora box:
Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)
In : s.actor.actor.The program 'python' received an X Window System
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 3710 error_code 10 request_code 143 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
On Thu, May 28, 2009 at 2:39 PM, Gael Varoquaux <
> On Thu, May 28, 2009 at 03:27:57PM -0400, Angus McMorland wrote:
> > I had tried it briefly before, and now, encouraged further by the
> > suggestion, I have fulfilled any expectation that the word
> > 'vigorously' might conjure, with no success. Ctrl-D also does nothing,
> > but Ctrl-\ still works, first time, to kill the session.
> I can a bit more information:
> resting ~/Projects/scipy/conference $ ipython -pylab
> from enPython 2.5.2 (r252:60911, Oct 5 2008, 19:24:49)
> Type "copyright", "credits" or "license" for more information.
> IPython 0.10.bzr.r1163 -- An enhanced Interactive Python.
> ? -> Introduction and overview of IPython's features.
> %quickref -> Quick reference.
> help -> Python's own help system.
> object? -> Details about 'object'. ?object also works, ?? prints more.
> Welcome to pylab, a matplotlib-based Python environment.
> For more information, type 'help(pylab)'.
> In : from enthought.mayavi import mlab
> In : s = mlab.test_surf()
> In : s.actor.actor.<tab>
> The program 'python' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAccess (attempt to access private resource denied)'.
> (Details: serial 6858 error_code 10 request_code 128 minor_code 5)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error()
> IPython-user mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-user