On Tue, Dec 2, 2008 at 12:09 PM, Eric Emsellem
<[EMAIL PROTECTED]> wrote:
> Really annoying but as mentioned before, I cannot get a set of commands which
> consistenly break the session, so...
Since there does not appear to be an easy diagnosis or fix, you may
want to consider switching your back
running the last ipython version now (0.9.1), and it does not help (got stuck
the same way).
The difference now is that ipython provides a message:
Warning: Timeout for mainloop thread exceeded
switching to nonthreaded mode (until mainloop wakes up again)
It seems that ipython developers did cat
:08:00 +0100
>> From: Eric Emsellem <[EMAIL PROTECTED]>
>> Subject: [Matplotlib-users] pylab or not... crashes or not
>>
>> - when I start a session with "ipython -pylab" I often get crashes
>> with my
>> session. When I mean "often", it me
Salut Eric,
> Date: Mon, 01 Dec 2008 20:08:00 +0100
> From: Eric Emsellem <[EMAIL PROTECTED]>
> Subject: [Matplotlib-users] pylab or not... crashes or not
>
> - when I start a session with "ipython -pylab" I often get crashes with my
> session. When I mean &
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 "
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
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
