[SciPy-Dev] Policy for minimum numpy version

[CJ Carey]

Most recently I've wished for np.full and np.full_like, though I admit that
they're very easy to work around.

More difficult to replace is np.partition and np.argpartition, which are
extremely useful in the few cases that they're needed but also non-trivial
to implement efficiently. Typically the work-arounds look like this (not my
code):
https://github.com/lemaoliu/Agtarbidir/blob/8762efcb29b37724c2af13f9393d1eaa5ec6faf8/numpy_compat.py

On Wed, Jul 27, 2016 at 12:52 PM, Eric Quintero <ericq at caltech.edu> wrote:

> Hi All,
>
> In gh-6058 <https://github.com/scipy/scipy/pull/gh-6058>, I’ve run into a
> test failure because a numpy function was not available in version 1.7 (the
> function being np.fft.rfftfreq). This is easy enough to work around, but I
> wonder when we should decide to move up the minimum required numpy version.
>
> Debian stable currently offers numpy 1.8.2. Ubuntu 12.04 LTS (which is EOL
> next April) is stuck on 1.6.1, so they’re already left behind. Ubuntu 14.04
> LTS has 1.8.2.
>
> Has anyone ran into compatibility issues with 1.7 before? In
> _lib._numpy_compat, there is another 1.7 workaround in place for
> np.testing.assert_warns.
>
> -Eric Q.
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160727/4f31a878/attachment.html>