Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upComments
richardotis
added
the
bug
label
Oct 17, 2015
richardotis
self-assigned this
Oct 17, 2015
This comment has been minimized.
This comment has been minimized.
|
See also numpy/numpy#6464 |
added a commit
that referenced
this issue
Oct 17, 2015
This comment has been minimized.
This comment has been minimized.
|
Fixed in 0.2.2. Please reopen if you find a case which was missed. |
richardotis
closed this
Oct 17, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
richardotis commentedOct 17, 2015
It looks like some stricter type casting conversion rules for ufuncs in numpy 1.10 has broken a whole bunch of code which uses
np.linalg.solveandnp.einsum. Some objects which I thought were of dtype float were apparently actually generic objects getting implicitly converted. It will take some time to fix.