-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Complement TypeAliasType #5486
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
base: main
Are you sure you want to change the base?
Complement TypeAliasType #5486
Conversation
fd8eda2 to
c9ed04a
Compare
c9ed04a to
36ee421
Compare
1e97ec8 to
8f7a6a8
Compare
|
was there problems? |
@youknowone I was doing some yak-shaving to bump the typing module, and then I wanted to bump the RustPython parser, and this is where I realized my lack of understanding of the PEPs involved and my lack of understanding of the underlying parser (compiler). Due to personal situation, I'm a bit confused about my study priorities and lack motivation. At the same time, new PR (#5590) had opened and I didn't want it to look like someone was working on them, so I closed PRs to avoid confusion. |
|
Thank you for sharing. Could you keep this opened until this feature is fully implemented to let other contributors can refer it for their work? |
|
No problem 👌🏻 |
Current PR Status
Currently, this pr stuck at the part to implement new syntax introduced at 3.13 syntax.
This pull request does:
typingmodule to3.13.1._typing.NoDefaultTypeAliasTypePyTypeFlags::IMMUTABLETYPEforTypeAliasType.TypeAliasType.__repr__implementation.References
TypeAliasTypeflags: https://github.com/python/cpython/blob/067145177975eadd61a0c907d0d177f7b6a5a3de/Objects/typevarobject.c#L1777