#65 New versions of numpy got rid of Oldnumeric

[Daniel Álvarez]

Newer versions of numpy (usually already pre-installed in linux OS) do not include Oldnumeric anymore. Biskit cannot initialize.
Substitute all oldnumeric calls to numpy functionalities.

[Raik Gruenberg]

Yes, acknowledged. Most of those where probably oldnumeric.nonzero() calls.
I was quite annoyed by the numpy nonzero 2-D return value and that's why used oldnumeric even in newer modules. Didn't know it would one day be phased out.

I see you already made the changes, great! All covered or are there still more to go? I don't have time to even look at this now... but a new maintainance release is needed anyway. Perhaps also time to transfer this project to github.

[Daniel Álvarez]

I adressesed it already. I didn't check the nonzero behaviour so I will take a look at this later this week if i find time.

Daniel Álvarez

Le 5 oct. 2015 à 16:16, Raik Gruenberg graik@users.sf.net a écrit :

Yes, acknowledged. Most of those where probably oldnumeric.nonzero() calls.
I was quite annoyed by the numpy nonzero 2-D return value and that's why used oldnumeric even in newer modules. Didn't know it would one day be phased out.

I see you already made the changes, great! All covered or are there still more to go? I don't have time to even look at this now... but a new maintainance release is needed anyway. Perhaps also time to transfer this project to github.

[bugs:#65] New versions of numpy got rid of Oldnumeric

Status: open
Group: v1.0 (example)
Created: Thu Oct 01, 2015 08:13 PM UTC by Daniel Álvarez
Last Updated: Thu Oct 01, 2015 08:13 PM UTC
Owner: nobody

Newer versions of numpy (usually already pre-installed in linux OS) do not include Oldnumeric anymore. Biskit cannot initialize.
Substitute all oldnumeric calls to numpy functionalities.

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/biskit/bugs/65/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Raik Gruenberg]

the conversion should look like this:
y = oldnumeric.nonzero(x)
to
y = numpy.nonzero(x)[0]

So a simple renaming will break things. The unittests should cover most of that though.

Thanks!

[Raik Gruenberg]

This issue has been closed with release 2.4.2 -- Note, this issue tracker is being retired. Issues are now tracked on github.