In the scientific crowd (if I may count myself among them),
Python2.3 is still used a lot. The enthought distribution
is very popular for teaching classes. So please keep 2.3
support on win32 going for a little while longer.
Thanks,
Mark
I assume you're responding to my comment "I suspect that there are relatively few Python 2.3 users on Windows anymore, so I say unmask it now." Let me clear up any misunderstanding immediately -- this was not me proposing to drop support for Python 2.3 on Windows. It was merely me proposing that we (well, Darren Dale) keep going forward with (2.3 compatible) development instead of being held back by a recently reported bug from a non-current version of matplotlib which I think is actually already fixed. That's what the "unmask it now" refers to -- unmasking Darren's latest work so it is active in the svn version of matplotlib.
I actually sent out a request for win32 folks to test my presumptive patch some weeks ago:
http://sourceforge.net/mailarchive/forum.php?thread_id=9967846&forum_id=36187
That exact test is still what's required for us to be sure my patch has worked, and apparently what the latest fuss is about.
Rest assured no one has any plans on disabling Python 2.3 support. My suggestion is simply not to hold back development due to lack of feedback from the win32 Python2.3 crowd. Mark, if you're willing act on that feedback request from a few weeks ago, that would be great.
Cheers!
Andrew
Mark Bakker wrote:
···
In the scientific crowd (if I may count myself among them),
Python2.3 is still used a lot. The enthought distribution
is very popular for teaching classes. So please keep 2.3
support on win32 going for a little while longer.Thanks,
Mark
+1 -- is breaking backward compatibility necessary? In addition to
the point above, python 2.4 uses a different compiler, and some
home-built extensions may not have been ported over to the new
compiler system yet. I'm sure that's out of pure laziness (speaking
for myself, anyway, but then I have a Windows box with working
python2.2, 2.3, and 2.4), so I suppose I can keep working with a
python 2.3 and matplotlib ~0.87.1.
--Matt Newville
···
On 4/5/06, Mark Bakker <markbak@...149...> wrote:
In the scientific crowd (if I may count myself among them),
Python2.3 is still used a lot. The enthought distribution
is very popular for teaching classes. So please keep 2.3
support on win32 going for a little while longer.
As far as I can tell, this discussion is coming up in the context of using the
subprocess module. The reason Andrew added the module to the mpl source was
to provide support for python-2.3. Maybe someone will correct me, but I dont
think there is any reason to worry about continued support of python-2.3.
···
On Wednesday 05 April 2006 17:40, Matt Newville wrote:
On 4/5/06, Mark Bakker <markbak@...149...> wrote:
> In the scientific crowd (if I may count myself among them),
> Python2.3 is still used a lot. The enthought distribution
> is very popular for teaching classes. So please keep 2.3
> support on win32 going for a little while longer.+1 -- is breaking backward compatibility necessary? In addition to
the point above, python 2.4 uses a different compiler, and some
home-built extensions may not have been ported over to the new
compiler system yet. I'm sure that's out of pure laziness (speaking
for myself, anyway, but then I have a Windows box with working
python2.2, 2.3, and 2.4), so I suppose I can keep working with a
python 2.3 and matplotlib ~0.87.1.
HI Andrew,
Thanks for clearing that up, and sorry for mis-reading your post.
FWIW, I don't keep up to date with the svn builds on Win32.
Anyway, thanks and sorry for butting in....
--Matt Newville