-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
MAINT: Update FutureWarning message. #9058
Conversation
The future structured array assignment change warned about in dtype_transfer.c will take place in NumPy 1.14, not 1.13.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'm assuming that this warning isn't present elsewhere
For the sake of linking PRs, this is due to #6053 being kicked back to 1.14
Do we want a release note mentioning that this feature is delayed? |
Hadn't occurred to me, but probably a good idea. I'll add that. |
I documented the whole future change in the release notes as it was missing from the 1.12.0 notes. |
doc/release/1.13.0-notes.rst
Outdated
in NumPy 1.14. Previously fields in the dst would be set to the value of the | ||
identically-named field in the src. In numpy 1.14 fields will instead be | ||
assigned 'by position': The n-th field of the dst will be set to the n-th | ||
field of the src array, Note that the ``FutureWarning`` raised in NumPy 1.12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, this time I'm sure about commas - this one shouldn't be here!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops.
c86070d
to
88d6edb
Compare
The future structured array assignment change warned about in
dtype_transfer.c will take place in NumPy 1.14, not 1.13.