John et al.,
Is this a reasonable time to put out 1.0.1? There have been quite a few bugfixes and other cleanups since 1.0. Most likely the biggest problem with 1.0 is my error in the tk show(), which you tripped over, and which prompted the thread below.
-------- Original Message --------
Subject: Re: [Matplotlib-users] show() blocks script execution for TkAgg from ipython -pylab
Date: Wed, 11 Aug 2010 09:35:24 -0700
From: Christoph Gohlke <cgohlke@...244...>
Ryan: you could try matplotlib-1.0.0.svn.win32-py2.6.exe from
http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib .It was built this
morning from svn.
On 8/11/2010 7:26 AM, Ryan Krauss wrote:
0.99.3 is more or less fine, but there is an annoying exception window
that pops up if you close IPython with a plot window open (using the
TkAgg backend). But in my mind this is less bothersome than having to
close all the plot windows every time I run a script (I tend to write
scripts that generate 5-10 plots at a minimum).
If I could easily build an installer from svn, I would try it. I
don't have any microsoft compilers installed on my windows computers.
On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss<ryanlists@...149...> wrote:
I need to role out a python install for my students. Classes start in
a week and a half. What should I do? The installation for most of
them needs to be fairly simple.
On Wed, Aug 11, 2010 at 2:25 AM, Eric Firing<efiring@...229...> wrote:
On 08/10/2010 05:43 PM, Ryan Krauss wrote:
I just upgraded my windows machine to matplotlib 1.0.0 and a simple
script such as
from pylab import *
from scipy import *
t = arange(0,1,0.01)
y = sin(2*pi*t)
Now halts execution when run from the ipython -pylab prompt. The same
commands typed at the commandline do not lead to show() halting
Is this expected behavior?
This was fixed three weeks ago in svn, both the maintenance branch and
the trunk. I made some changes in show() shortly before 1.0, trying to
get uniform and reasonable behavior in all backends, and I didn't quite
succeed. I think I got it all straightened out--but only after the
release, unfortunately. I hope it won't be too long before a 1.0.1
bugfix release can be made, but I am aware of no schedule.