On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers
ralf.gomm...@googlemail.comwrote:
On Fri, Feb 10, 2012 at 10:25 AM, David Cournapeau courn...@gmail.comwrote:
On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant
On Sat, Feb 11, 2012 at 9:08 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers ralf.gomm...@googlemail.com
wrote:
On Fri, Feb 10, 2012 at 10:25 AM, David Cournapeau courn...@gmail.com
wrote:
On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
On Sat, Feb 11, 2012 at 12:05 PM, David Cournapeau courn...@gmail.comwrote:
On Sat, Feb 11, 2012 at 9:08 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers
ralf.gomm...@googlemail.com
wrote:
On Fri, Feb 10, 2012 at 10:25 AM, David
On Sat, Feb 11, 2012 at 1:30 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
As Bruce said, 29 Feb 2012 and not 2014:
https://access.redhat.com/support/policy/updates/errata/
I think Bruce and me were not talking about the same RHEL version (4 vs 5).
Let me see if I can set up a buildbot
On Sat, Feb 11, 2012 at 4:08 PM, David Cournapeau courn...@gmail.comwrote:
On Sat, Feb 11, 2012 at 1:30 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
As Bruce said, 29 Feb 2012 and not 2014:
https://access.redhat.com/support/policy/updates/errata/
I think Bruce and me were not
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
On Sat, Feb 11, 2012 at 7:51 PM, Travis Oliphant tra...@continuum.iowrote:
NumPy 1.7 is due out in the next few weeks.
This depends on whether all the issues regarding the move to gcc 4.x on
Windows will be solved. Right now numpy is not releasable. Either those
issues get solved, or we have
On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant tra...@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
On 5 February 2012 07:19, Ralf Gommers ralf.gomm...@googlemail.com wrote:
On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant tra...@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
Hi All,
In the discussion on deprecating old macros in 1.7 as part of pull request
189 https://github.com/numpy/numpy/pull/189 the issue of how to move
numpy forward and start clearing the decks of accumulated cruft arose. The
proposal here is to make the 1.7 a long term support release that we
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
On Sat, Feb 4, 2012 at 3:03 PM, Travis Oliphant tra...@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
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
-Travis
On Feb 4, 2012, at 10:13 PM, Bruce Southey wrote:
On Sat, Feb 4, 2012 at 6:07 PM, Charles R Harris
charlesr.har...@gmail.com
On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant tra...@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
14 matches
Mail list logo
