Re: [Matplotlib-users] matplotlib-0.54 Win98 crash

[John H. <jdh...@ac...>]

>>>>> "Gary" == Gary Ruben <ga...@em...> writes:

    Gary> Hi John, I probably didn't make it clear, but TkAgg has
    Gary> problems too.  Here's what I know: Under 0.53.1 TkAgg and
    Gary> GTKAgg both worked fine, both when running the script
    Gary> directly from Windows Explorer in which case file
    Gary> association cause python to fire up in a DOS shell, and when
    Gary> running it from within SciTE or IDLE things are fine
    Gary> too. 0.54 has changed something.

Well, it's changed a lot.  The big dollar question is which of these
changes are causing these problems :-)

    Gary>  I tried grabbing and
    Gary> running a few examples from CVS as well as my own previously
    Gary> working examples. They behave consistently - GTKAgg no
    Gary> longer works at all

I need clarification here.  What does it mean "no longer works at
all".  If you open up a DOS command shell and run

  from matplotlib.matlab import *
  plot([1,2,3])
  show()

with 

  c:> python myscript.py -dGTKAgg

what happens?  When you run from windows explorer and get a traceback,
you often lose the DOS window that provides the required information.
So it's best to debug from a command shell, though admittedly most of
the windows shells suck.

    Gary>  and TkAgg works but only if I run it from DOS with a
    Gary> -dTkAgg option.  It may be a GUI conflict but it has only
    Gary> started to conflict with 0.54.  removing show() or replacing
    Gary> it with show(mainloop=False) seem to make no difference to
    Gary> the behaviour running TkAgg from SciTE.  

show(mainloop=False) would only be expected to have any effect with
GTK*, but I understand that it's not helping in that case either.

    Gary> I do notice that
    Gary> the python >>> prompt comes up in any DOS windows when
    Gary> running with the -dTkAgg option after the Tk plot window
    Gary> displays. Closing the window then leaves the python prompt
    Gary> and I have to ^Z it to shut it down. It's like it thinks it
    Gary> should be running in interactive mode, although 'interactive
    Gary> : False' is set in my .matplotlibrc This seems abnormal to
    Gary> me.

This is intentional.  Since Tkinter doesn't have a mainloop, we switch
python to interactive mode after TkAgg finishes it's business and the
Tk window remains open until the python shell is closed.

    Gary> In my original post I asked if anyone else had success or
    Gary> problems in Win98 and since noone replied, maybe we can
    Gary> assume that I'm one of the rare users who's still using
    Gary> it. Therefore, as much as I (and probably you) would like to
    Gary> get to the bottom of what's happening, it's probably Win98
    Gary> specific and therefore, can probably wait; at least until
    Gary> after my upcoming exams are over and I get a chance to

I would be surprised if it's win98 specific.  I haven't seen any
problems so far that were specific to just one windows OS.  They're
basically all the same as far as I can see, Microsoft just keeps
shrinkwrapping them and recharging you for them :-)  I have win98 at
home so I'll try and test a version there.

    Gary> really look into it some more. So I might go quiet for a few
    Gary> weeks unless you want me to try anything quick and specific.
    Gary> Finally, I hope you didn't lose the ecolor changes I made to
    Gary> errorbars and they might make it into a future version :-)

No, I missed them the first time but when cleaning out my inbox found
them and made an entry on the TODO list, so they'll get merged soon
enough.  Thanks.

If you could try the command shell test with GTKAgg that I asked for
above, that would be great.

JDH