John Hunter wrote: > On Mon, Dec 1, 2008 at 1:08 PM, Eric Emsellem > <[EMAIL PROTECTED]> wrote: >> Hi >> >> this may be a known problem (didn't find anything on this issue) but here it >> is: >> >> - when I start a session with "ipython -pylab" I often get crashes with my >> session. When I mean "often", it means really often like once everything >> 1/2h or >> so. A crash means that the command I just sent gets stuck and the only way >> for >> me to get it back is to kill the PID of the ipython process... >> >> The problem is that it is almost impossible to reproduce a systematic >> behaviour >> there so I cannot really send you a list of commands which results in a >> crash. >> It just happens (often). However, after someone suggested it, I now enter >> Ipython by a simple "ipython" and do immediately "from pylab import *". And >> then >> I have NO crashes whatsoever. >> >> any suggestion there? Is that normal? > > It is definitely not normal -- it almost never happens to me. Does it > help if you run TkAgg instead of GTKAgg. Are you importing/using > anything else when this is happening? What version of numpy are you > running?
Well I never use ipython -pylab and always use tkagg. It could be a race in the way ipython manage to do that: http://ipython.scipy.org/moin/Cookbook/InterruptingThreads What version of ipython are you using? Xavier ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
