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.
Eric
···
-------- 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...>
To: matplotlib-users@lists.sourceforge.net
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.
Christoph
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.
Thanks again,
Ryan
On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss<ryanlists@...149...> wrote:
Thanks.
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.
Thanks,
Ryan
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)
figure(1)
clf()
plot(t,y)
show()
Now halts execution when run from the ipython -pylab prompt. The same
commands typed at the commandline do not lead to show() halting
execution.
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.
Eric
Thanks,
Ryan
FWIW, I responded to a thread on the IPython list where someone else
was asking why show() was blocking execution on Windows 7. I think he
was really experiencing the tk show() problem from mpl. So, I think
this is causing issues with other users (in my opinion).
Ryan
···
On Wed, Aug 11, 2010 at 12:35 PM, Eric Firing <efiring@...229...> wrote:
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.
Eric
-------- 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...>
To: matplotlib-users@lists.sourceforge.net
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.
Christoph
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.
Thanks again,
Ryan
On Wed, Aug 11, 2010 at 9:09 AM, Ryan Krauss<ryanlists@...149...> wrote:
Thanks.
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.
Thanks,
Ryan
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)
figure(1)
clf()
plot(t,y)
show()
Now halts execution when run from the ipython -pylab prompt. The same
commands typed at the commandline do not lead to show() halting
execution.
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.
Eric
Thanks,
Ryan
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
I've been meaning to ask you the same thing :-). We probably need to
have a go at the bug tracker before 1.0.1, but I am happy to do a
bugfix release as soon as we are ready.
Or perhaps we should be a little more aggressive on our numbering.
Ie, bugfix releases could be 1.1.0 and 1.0.1, a micro release would be
for installer fixes and the like.
major numbers: significant new features, minor API breakage
minor numbers: significant bugfixes and near guaranteed API compat
micro: minor bugfixes, API compat
I think 1.0 understates the maturity of the project so we may want to
get to 2.0 in less than 10 years 
JDH
···
On Wed, Aug 11, 2010 at 12:35 PM, Eric Firing <efiring@...229...> wrote:
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.
Couldn’t we just do what Google does and put a “Beta” label on everything?
“Matplotlib Beta”
Sounds almost like a planet or something…
Ben Root
···
On Wed, Aug 11, 2010 at 1:27 PM, John Hunter <jdh2358@…149…> wrote:
On Wed, Aug 11, 2010 at 12:35 PM, Eric Firing <efiring@…229…> wrote:
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.
I’ve been meaning to ask you the same thing :-). We probably need to
have a go at the bug tracker before 1.0.1, but I am happy to do a
bugfix release as soon as we are ready.
Or perhaps we should be a little more aggressive on our numbering.
Ie, bugfix releases could be 1.1.0 and 1.0.1, a micro release would be
for installer fixes and the like.
major numbers: significant new features, minor API breakage
minor numbers: significant bugfixes and near guaranteed API compat
micro: minor bugfixes, API compat
I think 1.0 understates the maturity of the project so we may want to
get to 2.0 in less than 10 years
JDH
That used to be my attitude. Turns out there are a lot of legitimate
users who cannot (due to company IT policy) or will not use software
at 1.0 and below or in beta. It's a nice crutch for developers to say
"hey it's in beta so don't count on us not pulling the API rug out
from under you". We have historically been very cautious about
breaking API, and the code is mature and stable, so the version number
should reflect that in my view.
JDH
···
On Wed, Aug 11, 2010 at 1:32 PM, Benjamin Root <ben.root@...553...> wrote:
Couldn't we just do what Google does and put a "Beta" label on everything?
"Matplotlib Beta"
Sounds almost like a planet or something...