disable ufunc override for 1.9 release #4920
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think we should be ready then to prepare the 1.9 beta2, I really wanted to update our mingw toolchain for 1.9 too but I don't have the windows debugging experience to fix the issues in #4909, so that will be a task for 1.10. |
|
LGTM pending Travis. |
The ufunc override `__numpy_ufunc__` still has a few unresolved issues regarding its behavior towards Python operators see numpygh-4815. To avoid releasing numpy with an interface that might change in the next numpy version and to not further delay the 1.9 release it has been decided to disable the feature in 1.9.0.
charris
added a commit
that referenced
this pull request
Jul 30, 2014
disable ufunc override for 1.9 release
|
Thanks Julian. |
|
Also the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ufunc override
__numpy_ufunc__still has a few unresolved issuesregarding its behavior towards Python operators see gh-4815.
To avoid releasing numpy with an interface that might change in the next
numpy version and to not further delay the 1.9 release it has been
decided to disable the feature in 1.9.0.