Hello all,
While at SciPy this year, the IPython devs began discussing dropping Python
2.4 support. Or rational is this:
* New generator features in 2.5 would dramatically simplify our testing of
our Twisted using components.
* Being able to use absolute imports would simplify the packaging of some
external deps.
* The faster we get rid of 2.4 and 2.5 support (we are not getting rid of
2.5 yet) the faster we can transition to py3k.
But, this would mean that pylab mode for matplotlib would require either:
* Using IPython v 0.10 or below
* Using Python 2.5/2.6
We know that there are people still using Python 2.4, but at this point, we
feel the benefits outweight the costs. How do the matplotlib devs feel
about this?
As a side note, as of IPython 0.11, the IPython threaded shells (pylab
stuff) will be completely refactored. This will require matplotlib to make
some moderate changes to support the new interface. Thus, even if we don't
drop 2.4 support, matplotlib will have to decide how to handle the IPython
0.10->0.11 transition.
Cheers,
Brian
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
