[Numpy-discussion] Clarification sought on Scipy Numpy version requirements.
Charles R Harris
charlesr.harris at gmail.com
Sun Jun 21 11:13:11 EDT 2015
On Sun, Jun 21, 2015 at 7:14 AM, Ralf Gommers <ralf.gommers at gmail.com>
> On Fri, Jun 19, 2015 at 11:52 PM, Charles R Harris <
> charlesr.harris at gmail.com> wrote:
>> On Fri, Jun 19, 2015 at 3:05 PM, Sturla Molden <sturla.molden at gmail.com>
>>> Charles R Harris <charlesr.harris at gmail.com> wrote:
>>> > I'm looking to change some numpy deprecations into errors as well as
>>> > some deprecated functions. The problem I see is that
>>> > SciPy claims to support Numpy >= 1.5 and Numpy 1.5 is really, really,
>>> > So the question is, does "support" mean compiles with earlier versions
>>> > of Numpy ?
>>> It means there is a Travis CI build with NumPy 1.6.2. So any change to
>>> SciPy source code must compile with NumPy 1.6 and any later version of
>>> There is no Travis CI build with NumPy 1.5. I don't think we know for
>>> if it is really compatible with the current SciPy.
There is still a reference to 1.5 in Scipy, I forget where.
>> I guess this also raises the question of what versions of Scipy Numpy
>> needs to support.
> I'd treat Scipy like any other popular package that depends on Numpy. If a
> change in Numpy would break a Scipy version released in say the last 1.5
> years, then that's a problem. If it's a quite old Scipy, then it may be OK.
So that would be Scipy 0.13, looks like.
> I'm thinking of removing the noprefix.h, but it doesn't cost to leave it
>> in as it must be explicitly included by anyone who needs it. Hmm, maybe
>> best to leave it be, although I suspect anyone using it could just as well
>> use an earlier version of Numpy.
> Does noprefix.h even give you a deprecation warning now? Doesn't look like
> it to me, which means it should be left alone for quite a while.
Yeah, it's probably best to just leave it be.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion