On Thu, Dec 13, 2012 at 11:34 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
Time to raise this topic again. Opinions welcome.
As you know from the pull request discussion, big +1 from me too. I'm
also of the opinion with David C. and Brad that dropping 2.5 support
would be a good thing
So when upgrading everything you prefer to keep the bugs in 2.6 that were
squashed in 2.7? Who has taught IT managers that older and more buggy versions
of software are more professional and better for corporate environments?
Sturla
Den 14. des. 2012 kl. 05:14 skrev Raul Cota
On 14 Dec 2012 04:14, Raul Cota r...@virtualmaterials.com wrote:
+1 from me
For what is worth, we are just moving forward from Python 2.2 / Numeric
and are going to 2.6 and it has been rather painful because of the
several little details of extensions and other subtleties. I believe we
Point well taken. It is always a tradeoff / balancing act where you can
have 'anything' but not 'everything'. Where would the fun be if we could
have everything :) ? . In our situation, there were a couple of
extensions that did not work (at least out of the box) in Python 2.7.
Raul
On
A big +1 from me --- but I don't have anyone I know using 2.4 anymore
-Travis
On Dec 13, 2012, at 10:34 AM, Charles R Harris wrote:
Time to raise this topic again. Opinions welcome.
Chuck
___
NumPy-Discussion mailing list
As a point of reference, python 2.4 is on RH5/CentOS5. While RH6 is the
current version, there are still enterprises that are using version 5. Of
course, at this point, one really should be working on a migration plan and
shouldn't be doing new development on those machines...
Ben Root
+1, if someone wants to use an older version of Python they can use an
older version of numpy.
On Thu, Dec 13, 2012 at 10:36 AM, Travis Oliphant tra...@continuum.iowrote:
A big +1 from me --- but I don't have anyone I know using 2.4 anymore
-Travis
On Dec 13, 2012, at 10:34 AM,
On Thu, Dec 13, 2012 at 5:34 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Time to raise this topic again. Opinions welcome.
I am ok if 1.7 is the LTS. I would even go as far as dropping 2.5 as
well then (RHEL 6 uses python 2.6).
cheers,
David
On Thu, Dec 13, 2012 at 12:00 PM, David Cournapeau courn...@gmail.com wrote:
snip
I would even go as far as dropping 2.5 as well then (RHEL 6
uses python 2.6).
+1
Skipper
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
Yes, and ditto for SciPy.
With dropped 2.4 support we can also use the new memoryview syntax instead of
ndarray syntax in Cython. That is more important for SciPy, but it has some
relevance for NumPy too.
Sturla
Sendt fra min iPad
Den 13. des. 2012 kl. 17:34 skrev Charles R Harris
Targeting = 2.6 would be preferable to me. Several other packages including
IPython, support only Python = 2.6, = 3.2.
This change would help me from accidentally writing Python syntax which is
allowable in 2.6 2.7 (but not in 2.4 or 2.5).
Compiling a newer Python interpreter isn't very
On Thu, Dec 13, 2012 at 10:12 AM, Bradley M. Froehle brad.froe...@gmail.com
wrote:
Targeting = 2.6 would be preferable to me. Several other packages
including IPython, support only Python = 2.6, = 3.2.
This change would help me from accidentally writing Python syntax which is
allowable in
On 12/13/2012 09:39 AM, Benjamin Root wrote:
As a point of reference, python 2.4 is on RH5/CentOS5. While RH6 is the
current version, there are still enterprises that are using version 5.
Of course, at this point, one really should be working on a migration
plan and shouldn't be doing new
On Thu, Dec 13, 2012 at 6:36 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Thu, Dec 13, 2012 at 10:12 AM, Bradley M. Froehle
brad.froe...@gmail.com wrote:
Targeting = 2.6 would be preferable to me. Several other packages
including IPython, support only Python = 2.6, = 3.2.
+1 from me
For what is worth, we are just moving forward from Python 2.2 / Numeric
and are going to 2.6 and it has been rather painful because of the
several little details of extensions and other subtleties. I believe we
will settle there for a while. For companies like ours, it is a big
15 matches
Mail list logo
