-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update typing_extensions #10344
Update typing_extensions #10344
Conversation
Stubtest is unhappy because these names don't exist in the released version of typing-extensions yet. I think it's better to have them in typeshed already though, so that type checkers have more of a chance to pick up the new stubs in time for the next typing-extensions release. Maybe we should install typing-extensions from git in the stubtest workflow. |
Seems like I need to fight stubtest some more, will look into it later today. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Now it's only pytype that's complaining, but it seems to be dumping out the entire ast of @rchen152 could you take a look? This is trying to implement the recent typing-extensions change where we now re-export more of typing. |
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.
LGTM once the pytype errors are resolved!
Thanks! Excited for this to land |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'll take a look sometime this week! Just got back from a three-week vacation, so I'm working my way through my backlog. |
Ok, turns out this is a pretty easy fix! pytype's copy of the typing stub was missing ForwardRef. I'll release a fixed version next week. |
Copied from typeshed. Fixes pytype test failure in python/typeshed#10344. PiperOrigin-RevId: 548546490
I released pytype-2023.07.21, but it looks like typeshed can't update to it because of a dependency conflict (https://github.com/python/typeshed/actions/runs/5626188689/job/15246504135). I see that there's already a PR open in the pycln repo to fix this: hadialqattan/pycln#209. |
Yeah, I noticed this issue when working on #10492 yesterday :/ hopefully the pycln maintainer will be okay with widening the libcst pin |
(Could we just drop pycln? I think we're already using ruff + I don't like using things that pin dependencies) |
This comment has been minimized.
This comment has been minimized.
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
Thanks @JelleZijlstra and @rchen152 both! |
No description provided.