Skip to content

Fixes for numpy 1.14.0 compatibility #1246

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

Merged
merged 1 commit into from
Jan 11, 2018
Merged

Conversation

jagerman
Copy link
Member

  • UPDATEIFCOPY is deprecated, replaced with similar (but not identical)
    WRITEBACKIFCOPY; trying to access the flag causes a deprecation
    warning under numpy 1.14, so just check the new flag there.
  • Numpy repr formatting of floats changed in 1.14.0 to [1., 2., 3.]
    instead of the pre-1.14 [ 1., 2., 3.]. Updated the tests to
    check for equality with the repr(...) value rather than the
    hard-coded (and now version-dependent) string representation.

- UPDATEIFCOPY is deprecated, replaced with similar (but not identical)
  WRITEBACKIFCOPY; trying to access the flag causes a deprecation
  warning under numpy 1.14, so just check the new flag there.
- Numpy `repr` formatting of floats changed in 1.14.0 to `[1., 2., 3.]`
  instead of the pre-1.14 `[ 1.,  2.,  3.]`.  Updated the tests to
  check for equality with the `repr(...)` value rather than the
  hard-coded (and now version-dependent) string representation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant