Repository navigation
MAINT/DOC: Use builtin when np.{x} is builtins.{x}. - #9517
Merged
Merged
Conversation
This is the case for x in {int, bool, str, float, complex, object}.
Using the np.{x} version is deceptive as it suggests that there is a
difference. This change doesn't affect any external behaviour. The
`long` type is missing in python 3, so np.long is still useful
Member
|
You could have force-pushed over the previous PR I think, but whatever. I'm guessing this is you approving of that changeset? |
Member
|
|
Member
Author
|
Yes, I'll merge when the tests complete. |
Member
Author
I usually download and apply the patch, |
Member
|
Seems I missed the .pyx files here |
9 of 14 tasks
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
2 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.
Rebase of #9508.
This is the case for x in {int, bool, str, float, complex, object}. Using the np.{x} version is deceptive as it suggests that there is a difference. This change doesn't affect any external behavour. The
longtype is missing in python 3, so np.long is still useful. Likewise with np.unicode.It may be difficult to deprecate these (#6103), but there's no reason we should be using them within our own code, or within our documentation.
Simple find and replace of np.(int|complex|object|str|bool|float)\b with $1.