Including fix for #1637 in 1.5.1 ?
Hi, I just committed a quick fix for http://projects.scipy.org/numpy/ticket/1637. I did want to include it for 1.5.x branch as it is already in RC stage, but it may still be useful to do so if the release managers think it is appropriate (there is a test for it): http://github.com/numpy/numpy/commit/cdcbaa4ce4b47a7bfd8905222124fd22460252a... cheers, David
On Sun, Oct 31, 2010 at 2:46 PM, David Cournapeau <cournape@gmail.com> wrote:
Hi,
I just committed a quick fix for http://projects.scipy.org/numpy/ticket/1637. I did want to include it for 1.5.x branch as it is already in RC stage, but it may still be useful to do so if the release managers think it is appropriate (there is a test for it): http://github.com/numpy/numpy/commit/cdcbaa4ce4b47a7bfd8905222124fd22460252a...
I would prefer not to include it at this stage - this doesn't seem an important enough bug to me to throw in compiled code at the last moment. Backporting after 1.5.1 is released may make sense though, in case there's a 1.5.2. Cheers, Ralf
On Mon, Nov 1, 2010 at 7:39 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Sun, Oct 31, 2010 at 2:46 PM, David Cournapeau <cournape@gmail.com> wrote:
Hi,
I just committed a quick fix for http://projects.scipy.org/numpy/ticket/1637. I did want to include it for 1.5.x branch as it is already in RC stage, but it may still be useful to do so if the release managers think it is appropriate (there is a test for it): http://github.com/numpy/numpy/commit/cdcbaa4ce4b47a7bfd8905222124fd22460252a...
I would prefer not to include it at this stage - this doesn't seem an important enough bug to me to throw in compiled code at the last moment.
Ok, no problem. I will backport it to 1.5.x, if only to help during the 1.5 -> 2.0 transition. cheers, David
participants (2)
-
David Cournapeau -
Ralf Gommers