ENH: np.testing.decorators: Use Py3k compatible raise syntax - #353
Merged
Merged
Conversation
Member
There was a problem hiding this comment.
Good catch. We tried to clean up all the string error syntax, but obviously we missed some.
Member
|
Further fixes like this are welcome. |
charris
added a commit
that referenced
this pull request
Jul 12, 2012
ENH: np.testing.decorators: Use Py3k compatible raise syntax
luyahan
pushed a commit
to plctlab/numpy
that referenced
this pull request
Apr 25, 2024
feat: Add vcgez[q|d|s]_[s8|s16|s32|s64|f32|f64]
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
IPython is currently working towards improved Py3k support in the master branch (i.e., reducing the number of necessary 2to3 fixes). As you may know, we maintain a copy of numpy.testing.decorators so as to eliminate external dependencies.
It'd be convenient for us if you were to update the
raisesyntax in this one file. There is only one instance ofraise E, V(the rest use the newerraise E(V)syntax) so it's a simple one line update.