Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
bpo-46553: allow bare typing.ClassVar annotations#30983
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
These are used in the wild and covered by dataclasses unit tests.Several static type checkers support this pattern.Note we adjust one test from ClassVar[ClassVar] toClassVar[ClassVar[int]] so that it still fails. This is surprising, butnot a result of weirdness we're doing in this patch. This is alimitation of the current way runtime type checking works that this caseis allowed when bare special forms are allowed. For example, before thispatch `ClassVar[Final]` is a valid annotation despite nesting theseforms being generally disallowed. Addressing this limitation could befuture work.
gvanrossum approved these changesJan 28, 2022
bedevere-bot commentedJan 28, 2022
@gvanrossum: Please replace |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
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.
Uh oh!
There was an error while loading.Please reload this page.
This is a simple matter of just adding
ClassVarto the list of types allowed to be bare before the later call that raises for bare types.These are used in the wild and covered by dataclasses unit tests.
Several static type checkers support this pattern.
Note we adjust one test from
ClassVar[ClassVar]toClassVar[ClassVar[int]]so that it still fails. This is surprising, butnot a result of weirdness we're doing in this patch. This is a
limitation of the current way runtime type checking works that this case
is allowed when bare special forms are allowed. For example, before this
patch
ClassVar[Final]is a valid runtime annotation despite nesting theseforms being generally disallowed, so it's expected allowing bare
ClassVarmakes
ClassVar[ClassVar]valid as well.https://bugs.python.org/issue46553