28 Jun 2012 14:25
28 Jun 2012 15:53
Re: Dropping support for Python 2.4 in NumPy 1.8
David Cournapeau <cournape <at> gmail.com>
2012-06-28 13:53:14 GMT
2012-06-28 13:53:14 GMT
Hi Travis, On Thu, Jun 28, 2012 at 1:25 PM, Travis Oliphant <travis <at> continuum.io> wrote: > Hey all, > > I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that? I think it would depend on 1.7 state. I am unwilling to drop support for 2.4 in 1.8 unless we make 1.7 a LTS, that would be supported up to 2014 Q1 (when RHEL5 stops getting security fixes - RHEL 5 is the one platform that warrants supporting 2.4 IMO) In my mind, it means 1.7 needs to be stable. Ondrej (and others) work to make sure we break neither API or ABI since a few releases would help achieving that. David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 16:44
Re: Dropping support for Python 2.4 in NumPy 1.8
Olivier Delalleau <shish <at> keba.be>
2012-06-28 14:44:54 GMT
2012-06-28 14:44:54 GMT
2012/6/28 David Cournapeau <cournape <at> gmail.com>
Hi Travis,I think it would depend on 1.7 state. I am unwilling to drop support
On Thu, Jun 28, 2012 at 1:25 PM, Travis Oliphant <travis <at> continuum.io> wrote:
> Hey all,
>
> I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that?
for 2.4 in 1.8 unless we make 1.7 a LTS, that would be supported up to
2014 Q1 (when RHEL5 stops getting security fixes - RHEL 5 is the one
platform that warrants supporting 2.4 IMO)
In my mind, it means 1.7 needs to be stable. Ondrej (and others) work
to make sure we break neither API or ABI since a few releases would
help achieving that.
David
As a user stuck with Python 2.4 for an undefined period of time, I would definitely appreciate a long-term support release that would retain Python 2.4 compatibility.
-=- Olivier
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 17:08
Re: Dropping support for Python 2.4 in NumPy 1.8
Ralf Gommers <ralf.gommers <at> googlemail.com>
2012-06-28 15:08:36 GMT
2012-06-28 15:08:36 GMT
On Thu, Jun 28, 2012 at 4:44 PM, Olivier Delalleau <shish <at> keba.be> wrote:
Hi, I have an honest question for you (and other 2.4 users). Many packages have long since dropped 2.4 compatibility. IPython and scikit-learn require 2.6 as a minimum, scikits-image and statsmodels 2.5. So what do you do about those packages, not use them at all, or use an older version?
All those packages are improving (in my opinion) at a much faster rate than numpy. So if you do use them, up-to-date versions of those are likely to be more useful than a new version of numpy. In that light, does keeping 2.4 support really add significant value for you?
Regards,
Ralf
As a user stuck with Python 2.4 for an undefined period of time, I would definitely appreciate a long-term support release that would retain Python 2.4 compatibility.2012/6/28 David Cournapeau <cournape <at> gmail.com>Hi Travis,I think it would depend on 1.7 state. I am unwilling to drop support
On Thu, Jun 28, 2012 at 1:25 PM, Travis Oliphant <travis <at> continuum.io> wrote:
> Hey all,
>
> I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that?
for 2.4 in 1.8 unless we make 1.7 a LTS, that would be supported up to
2014 Q1 (when RHEL5 stops getting security fixes - RHEL 5 is the one
platform that warrants supporting 2.4 IMO)
In my mind, it means 1.7 needs to be stable. Ondrej (and others) work
to make sure we break neither API or ABI since a few releases would
help achieving that.
David
Hi, I have an honest question for you (and other 2.4 users). Many packages have long since dropped 2.4 compatibility. IPython and scikit-learn require 2.6 as a minimum, scikits-image and statsmodels 2.5. So what do you do about those packages, not use them at all, or use an older version?
All those packages are improving (in my opinion) at a much faster rate than numpy. So if you do use them, up-to-date versions of those are likely to be more useful than a new version of numpy. In that light, does keeping 2.4 support really add significant value for you?
Regards,
Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 17:15
Re: Dropping support for Python 2.4 in NumPy 1.8
Olivier Delalleau <shish <at> keba.be>
2012-06-28 15:15:18 GMT
2012-06-28 15:15:18 GMT
2012/6/28 Ralf Gommers <ralf.gommers <at> googlemail.com>
On Thu, Jun 28, 2012 at 4:44 PM, Olivier Delalleau <shish <at> keba.be> wrote:As a user stuck with Python 2.4 for an undefined period of time, I would definitely appreciate a long-term support release that would retain Python 2.4 compatibility.2012/6/28 David Cournapeau <cournape <at> gmail.com>Hi Travis,I think it would depend on 1.7 state. I am unwilling to drop support
On Thu, Jun 28, 2012 at 1:25 PM, Travis Oliphant <travis <at> continuum.io> wrote:
> Hey all,
>
> I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that?
for 2.4 in 1.8 unless we make 1.7 a LTS, that would be supported up to
2014 Q1 (when RHEL5 stops getting security fixes - RHEL 5 is the one
platform that warrants supporting 2.4 IMO)
In my mind, it means 1.7 needs to be stable. Ondrej (and others) work
to make sure we break neither API or ABI since a few releases would
help achieving that.
David
Hi, I have an honest question for you (and other 2.4 users). Many packages have long since dropped 2.4 compatibility. IPython and scikit-learn require 2.6 as a minimum, scikits-image and statsmodels 2.5. So what do you do about those packages, not use them at all, or use an older version?
All those packages are improving (in my opinion) at a much faster rate than numpy. So if you do use them, up-to-date versions of those are likely to be more useful than a new version of numpy. In that light, does keeping 2.4 support really add significant value for you?
I just don't use any package that is not Python 2.4-compatible. The application I currently work with requires numpy, scipy and theano.
I might not need new features from newer numpy versions (not sure), but fixes for bugs and future compatibility issues that may come up would be nice.
-=- Olivier
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 16:54
Re: Dropping support for Python 2.4 in NumPy 1.8
Andreas Hilboll <lists <at> hilboll.de>
2012-06-28 14:54:00 GMT
2012-06-28 14:54:00 GMT
> Hi Travis, > > On Thu, Jun 28, 2012 at 1:25 PM, Travis Oliphant <travis <at> continuum.io> > wrote: >> Hey all, >> >> I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not >> the 1.7 release). What does everyone think of that? > > I think it would depend on 1.7 state. I am unwilling to drop support > for 2.4 in 1.8 unless we make 1.7 a LTS, that would be supported up to > 2014 Q1 (when RHEL5 stops getting security fixes - RHEL 5 is the one > platform that warrants supporting 2.4 IMO) +1 for the LTS "requirement". There are many people out there who cannot/wantnot install their own python just to support a new NumPy release. Unless, of course, there's compelling reasons to drop support for Python 2.4 (almost) immediately. _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 16:32
Re: Dropping support for Python 2.4 in NumPy 1.8
Richard Hattersley <rhattersley <at> gmail.com>
2012-06-28 14:32:33 GMT
2012-06-28 14:32:33 GMT
The project/environment we work with already targets Python 2.7, so it'd be fine for us and our collaborators. But it's hard to comment in a more altruistic way without knowing the impact of the change. Is it possible to summarise the benefits? (e.g. Simplifies NumPy codebase; allows better support for XXX under 2.5+; ...)
On 28 June 2012 13:25, Travis Oliphant <travis <at> continuum.io> wrote:
Hey all,
I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that?
-Travis
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion <at> scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion <at> scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 Jun 2012 16:51
Re: Dropping support for Python 2.4 in NumPy 1.8
John Hunter <jdh2358 <at> gmail.com>
2012-06-28 14:51:32 GMT
2012-06-28 14:51:32 GMT
On Thu, Jun 28, 2012 at 7:25 AM, Travis Oliphant <travis <at> continuum.io> wrote: > Hey all, > > I'd like to propose dropping support for Python 2.4 in NumPy 1.8 (not the 1.7 release). What does everyone think of that? As a tangential point, MPL is dropping support for python2.4 in it's next major release. As such we have put a lot of effort in making our upcoming point release extremely stable since it is likely to be the last 2.4 release. Our next major release, either designated 1.2 or 2.0 TBT) will have python3 support, and it seemed to much to try and support python versions from 2.4 on up.
RSS Feed