-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
TYP: resolve mypy errors in core/arrays/_ranges.py #52943
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
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
Is the result incorrect, or the type-hint incorrect? In general, fixing type-hints shouldn't change behavior. But if this function is supposed to return a Python integer then this is okay.
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.
The function signature is this:
which I interpreted as the function returning a Python integer, would that be correct?
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.
That is one possibility. The other possibility is that the signature is incorrect. Looking at the implementation, it seems clear to me this was meant to return a NumPy integer:
A look through the git blame shows this function having type-hints added after the initial implementation and prior to it being type-checked (likely because NumPy didn't have type-hints). With all this, it seems much more likely that the signature, and not the implementation, is incorrect.
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.
I see, that makes sense! I've pushed the changes I've made to the function—I was unsure about one thing: in the function
_generate_range_overflow_safe
line 160, the variablemidpoint
is assigned the result of recursively calling the function, and then repassed in as a parameter. I casted this to an integer to match the function signature, but I wasn't sure if this was the right way to go about it, or if theendpoint
parameter was supposed to be annp.int64
as well. However, in the function,endpoint
is casted tonp.int64
, so I assume that the function signature of it being a Pythonint
is correct.