[Numpy-discussion] On making Numpy 1.7 a long term support release.
Sun Feb 5 00:33:49 CST 2012
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 2.8
On Feb 4, 2012, at 10:13 PM, Bruce Southey wrote:
> On Sat, Feb 4, 2012 at 6:07 PM, Charles R Harris
> <firstname.lastname@example.org> wrote:
>> On Sat, Feb 4, 2012 at 3:03 PM, Travis Oliphant <email@example.com> wrote:
>>> We are spending a lot of time on NumPy and will be for the next few
>>> months. I think that 1.8 will be a better long term release. We need a few
>>> more fundamental features yet.
>>> Look for a roadmap document for discussion from Mark Wiebe and I within
>>> the week about NumPy 1.8 which has a target release of June 2012.
>> Looking forward to that document.
>> NumPy-Discussion mailing list
> A suitable long term release would include deprecating old macros,
> datetime and einsum. While I would like to include NA, I am rather
> concerned with the recent bugs that have been uncovered with it. So I
> am rather wary of having to forced to backport fixes simply because
> someone said we would "support with bug fixes for the next 2-3 years".
> Rather at least clearly indicate that not every fix will be
> I propose that we use this opportunity end support for Python 2.4
> especially since Red Hat Enterprise Linux (RHEL) 4 is February 29th,
> 2012. According to SourceForge, the last available binary release for
> Python 2.4 was for numpy 1.2.1 (released 2008-10-29). There is still
> quite a few downloads (3769) of the Python 2.5 numpy 1,6.1 binary.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion