You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This occurs since the multiarray module (and, hence, also umath) needs some initialization before it works correctly, and apparently some cleanup code assumes the initialization really has been performed before the interpreter is exited. The initialization is done on the Python side when numpy.core is imported.
I don't think this is a bug that can occur during normal operation (you don't get it from import numpy.core.umath), so closing as a wontfix.
While it shouldn't occur in normal operation, and wontfix is probably the right choice, it is worth noting that this is triggered by pylint 0.20.0 - see http://www.logilab.org/ticket/23009 .
Original ticket http://projects.scipy.org/numpy/ticket/1462 on 2010-04-23 by @drnlm, assigned to unknown.
As pointed out by Hodgestar on #scipy
However
The bug is present in numpy 1.3, but is reproducible using trunk on the sparc buildbot.
The text was updated successfully, but these errors were encountered: