[Numpy-discussion] On making Numpy 1.7 a long term support release.

mark florisson markflorisson88@gmail....
Fri Feb 10 04:20:29 CST 2012


On 5 February 2012 07:19, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
>
>
> On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant <travis@continuum.io> 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
>> 2.8
>>
> +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.

The with statement works just fine in python 2.5, all you have to do
is 'from __future__ import with_statement'. As for str.format, well...

> Ralf
>
>>
>>
>>
>> On Feb 4, 2012, at 10:13 PM, Bruce Southey wrote:
>>
>> > On Sat, Feb 4, 2012 at 6:07 PM, Charles R Harris
>> > <charlesr.harris@gmail.com> wrote:
>> >>
>> >>
>> >> On Sat, Feb 4, 2012 at 3:03 PM, Travis Oliphant <travis@continuum.io>
>> >> 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.
>> >>
>> >> Chuck
>> >>
>> >> _______________________________________________
>> >> NumPy-Discussion mailing list
>> >> NumPy-Discussion@scipy.org
>> >> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>> >>
>> >
>> > 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
>> > backported.
>> >
>> > 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.
>> >
>> > Bruce
>> > _______________________________________________
>> > NumPy-Discussion mailing list
>> > NumPy-Discussion@scipy.org
>> > http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>


More information about the NumPy-Discussion mailing list