Change types in "builtins" and "types" modules to have __new__ instead of __init__, where necessary #10761
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.
This means that calls to eg
range.__new__(range, 0)
will be checked correctly. The most common case for this is if a subclass of range makes its own__new__
method, and callssuper().__new__
(although some of the classes affected by this PR cannot be subclassed).I have deliberately ignored the reversed class, because it is the subject of its own ongoing PR, #10655.