Skip to content

Remove vendored typing-extensions #13336

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ichard26
Copy link
Member

It's a shockingly large dependency that does effectively nothing at runtime for us.

Depends on Textualize/rich#3700.

@ichard26 ichard26 added type: refactor Refactoring code project: vendored dependency Related to a vendored dependency labels Apr 15, 2025

if TYPE_CHECKING:
# TODO: import from typing once Python 3.10 is dropped.
from pip._vendor.typing_extensions import ParamSpec
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should import directly from typing_extensions and then add it's to the mypy pre commit additional dependencies:

additional_dependencies: [

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I need to fix the vendoring imports. vendoring is complaining because pip._vendor.typing_extensions does not exist anymore. I'll do that once Rich accepts my PR and cuts a new release.

@pfmoore
Copy link
Member

pfmoore commented Apr 15, 2025

Please be aware of #13313. I have been holding off on merging it, so that I can include any last minute upgrades to our dependencies before the release, but I don't want to get in a merge mess with this.

If you're hoping for this to go into 25.1, let me know and I can merge #13313, to give you a stable basis to work from.

@pfmoore
Copy link
Member

pfmoore commented Apr 15, 2025

Ah, I just noticed this relies on the rich PR, so I imagine it won't make it into 25.1 - that would need the rich PR to land, and a new release of rich, all within a week.

@ichard26
Copy link
Member Author

I imagine it won't make it into 25.1

Yup :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants