pylab or not... crashes or not

Community matplotlib-users
1

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?

thanks
Eric

P.S.: OpenSuse 11.0 or 10.3 (two machines showing similar behaviour)
matplotlib version 0.98.3

verbose.level helpful

interactive is True

units is True

platform is linux2

backend GTKAgg version 2.10.6

Python 2.5.1 (r251:54863, Aug 1 2008, 00:35:20)
IPython 0.8.1 -- An enhanced Interactive Python.

2

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?

···

On Mon, Dec 1, 2008 at 1:08 PM, Eric Emsellem <emsellem@...419...> 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?

3

John Hunter wrote:

···

On Mon, Dec 1, 2008 at 1:08 PM, Eric Emsellem > <emsellem@...419...> 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