[Numpy-discussion] Why is this old bug still present?

[Elliot Hallmark]

Sorry for the noob question.

On numpy 10.4.1, I am bit by this:
https://github.com/numpy/numpy/issues/4185

But it has been fixed 6 months ago:
https://github.com/numpy/numpy/issues/6740

Do I need to compile numpy to get this fix on debian sid? Would anaconda be
up to date enough?

Elliot

[Sean Mehta]

On numpy 10.4.1,  I am bit by this: https://github.com/numpy/numpy/issues/4185

 
I assume you mean 1.10.4?
 

But it has been fixed 6 months ago: https://github.com/numpy/numpy/issues/6740
Do I need to compile numpy to get this fix on debian sid? Would anaconda be up to date enough?

 
This fix was included in 1.11.0. My Anaconda installation hasn't updated
to 1.11.0 yet, although their package list [0] includes the 1.11.0
packages. Although I don't use Debian, a quick search in the Debian
unstable package list [1] seems to suggest that 1.11.0 is available.

I ended up building 1.11.0 manually for myself.

[0] http://repo.continuum.io/pkgs/free/linux-64/
[1]
https://packages.debian.org/search?keywords=numpy&searchon=names&suite=unstable&section=all
 

[Elliot Hallmark]

Thanks! Man, I got every one of those numbers in the wrong place...