-
-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeAliasType is always generic when type_params=()
is passed.
#124498
Labels
Comments
sobolevn
added a commit
to sobolevn/cpython
that referenced
this issue
Sep 25, 2024
sobolevn
added a commit
that referenced
this issue
Sep 26, 2024
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 26, 2024
…rams=()` (pythonGH-124499) (cherry picked from commit abe5f79) Co-authored-by: sobolevn <mail@sobolevn.me>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Sep 26, 2024
…rams=()` (pythonGH-124499) (cherry picked from commit abe5f79) Co-authored-by: sobolevn <mail@sobolevn.me>
This was referenced Sep 26, 2024
Merged
sobolevn
added a commit
that referenced
this issue
Sep 26, 2024
Yhg1s
pushed a commit
that referenced
this issue
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Bug description:
I realized that the
type_params
parameter ofTypeAliasType
behaves differently when it is omitted vs passing an empty tuple()
, in the latter case the resulting instance is always subscriptable. I doubt this is an undocumented feature.CPython versions tested on:
3.13
Operating systems tested on:
Linux
Linked PRs
TypeAliasType
not to be generic, whentype_params=()
#124499TypeAliasType
not to be generic, whentype_params=()
(GH-124499) #124603TypeAliasType
not to be generic, whentype_params=()
(GH-124499) #124604The text was updated successfully, but these errors were encountered: