| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…thonGH-30926) Previously this didn't matter because there weren't any valid code paths that could trigger a type check with a special form, but after the bug fix for `Annotated` wrapping special forms it's now possible to annotate something like `Annotated['ClassVar[int]', (3, 4)]`. This change would also be needed for proposed future changes, such as allowing `ClassVar` and `Final` to nest each other in dataclasses. (cherry picked from commit ced5005) Co-authored-by: Gregory Beauregard <greg@greg.red>
|
@GBeauregard and @gvanrossum: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
|
@GBeauregard and @gvanrossum: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
|
@GBeauregard and @gvanrossum: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Previously this didn't matter because there weren't any valid code paths
that could trigger a type check with a special form, but after the bug
fix for Annotated wrapping special forms it's now possible to annotate
something like Annotated['ClassVar[int]', (3, 4)]. This change would
also be needed for proposed future changes, such as allowing ClassVar
and Final to nest each other in dataclasses.
(cherry picked from commit ced5005)
Co-authored-by: Gregory Beauregard greg@greg.red
https://bugs.python.org/issue46539