objrange: Allow return of non-small ints. #17685
Open
+29
−3
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.
Summary
Closes #17684.
Testing
I wrote new tests & ran the unix coverage tests locally.
Trade-offs and Alternatives
Given that values between the "small int" range and "machine int" range never worked with range(), maybe non "small int"
range() arguments should be rejected instead. However, this would be a bit contradictory as you expect to have ranges with elements up to
sys.maxsize
at least.