Conversation
…subclassed Among the built-in classes that can't be subclassed, only bool documents it. memoryview, range, and slice behave the same but say nothing, so it can only be found out by trying. Add the same note to those three. The wording mirrors the existing bool entry, minus the "further" that applies only to bool (which subclasses int).
Documentation build overview
410 files changed ·
|
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
1 participant
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.
Among the built-in classes that can't be subclassed, only
booldocuments it.memoryview,range, andslicebehave the same but say nothing, so it can only be found out by trying. Add the same note to those three.The wording mirrors the existing
boolentry, minus the "further" that applies only tobool(which subclassesint). Confirmed at tip: subclassing each raisesTypeError(they lackPy_TPFLAGS_BASETYPE), whileintandlistallow it.This is the note the issue author proposed, and the thread confirmed all four are intentional rather than oversights. The
typesmodule classes mentioned in the issue are documented separately and are out of scope here.