[Numpy-discussion] On making Numpy 1.7 a long term support release.
Sat Feb 11 12:51:50 CST 2012
NumPy 1.7 is due out in the next few weeks. This will obviously support 2.4. It can be used for as long as people want.
Right now, there is a plan for NumPy 1.8 to be released in the summer which will have much attention paid to it in order to improve the documentation, add bug-fixes, as well as make feature additions. Right now, the plan is to have that release support 2.5, however, major bug-fixes will be back-ported to the 1.7 series as patches are available. I suspect that different organizations will use different versions of NumPy as their own LTS. I plan on encouraging people to use 1.8 as the LTS.
Work on NumPy 2.0 is already underway, but it will likely not be ready until January of 2013 at the earliest. Of course, there may be happy circumstances that accelerate that plan and other events that delay it. But, that is my best guess at the moment.
On Feb 10, 2012, at 3:25 AM, David Cournapeau wrote:
> On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
> <firstname.lastname@example.org> wrote:
>> On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant <email@example.com> wrote:
>>> I think supporting Python 2.5 and above is completely fine. I'd even be
>>> in favor of bumping up to Python 2.6 for NumPy 1.7 and certainly for NumPy
>> +1 for dropping Python 2.5 support also for an LTS release. That will make
>> it a lot easier to use str.format() and the with statement (plus many other
>> things) going forward, without having to think about if your changes can be
>> backported to that LTS release.
> At the risk of sounding like a broken record, I would really like to
> stay to 2.4, especially for a long term release :) This is still the
> basis used by a lots of long-term python products. If we can support
> 2.4 for a LTS, I would then be much more comfortable to allow bumping
> to 2.5 for 1.8.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion