-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Properly check for typing_extensions variant of TypeAliasType
#10713
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
Conversation
CodSpeed Performance ReportMerging #10713 will not alter performanceComparing Summary
|
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||
|
please review |
|
Thanks for the investigation and for the PR. I had this issue in my mind for some time now, and actually there's some other places where we're not careful enough (e.g. |
Sure thing! |
|
@Viicos I'd appreciate if this gets merged relatively quickly so the daily typing-extensions workflow that runs the pydantic test suite starts passing again. (Of course there are other workarounds; we could temporarily disable the pydantic tests, or just close the issue every day.) |
|
Ah didn't know that, I'll merge immediately and rebase on my working branch! |
Viicos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Daraan
typing & recent typing_extensions.TypeAliasType backport for Python 3.12, 3.13typing_extensions variant of TypeAliasType
Change Summary
Added support for recent
typing_extensions.TypeAliasTypefrom python/typing_extensions#477 that cause tests to fail currently.Related issue number
fix #10711
python/typing_extensions#493
Checklist
Selected Reviewer: @sydney-runkle