New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression on numpy 1.10 #24

Closed
richardotis opened this Issue Oct 17, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@richardotis
Collaborator

richardotis commented Oct 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.solve and np.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.

@richardotis richardotis added the bug label Oct 17, 2015

@richardotis richardotis self-assigned this Oct 17, 2015

@richardotis

This comment has been minimized.

Collaborator

richardotis commented Oct 17, 2015

See also numpy/numpy#6464

richardotis added a commit that referenced this issue Oct 17, 2015

@richardotis

This comment has been minimized.

Collaborator

richardotis commented Oct 17, 2015

Fixed in 0.2.2. Please reopen if you find a case which was missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment