Skip to content

mypy 1.16 has new dependency pathspec #19275

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

Open
kaddkaka opened this issue Jun 11, 2025 · 9 comments
Open

mypy 1.16 has new dependency pathspec #19275

kaddkaka opened this issue Jun 11, 2025 · 9 comments

Comments

@kaddkaka
Copy link

Documentation

mypy 1.15 does not have a dependency on python package pathspec but mypy 1.16 does. Is this something you usually document (in release notes?) or somewhere else?

@hauntsaninja
Copy link
Collaborator

No, like most Python packages, we document our dependencies in the packaging metadata

@jorenham
Copy link
Contributor

I believe that @kaddkaka wants to know why mypy now requires pathspec.

@brianschubert
Copy link
Collaborator

Linking #18696 for context

@jorenham
Copy link
Contributor

jorenham commented Jun 12, 2025

The --exclude-gitignore is a very handy feature. But if that's the only reason for requiring pathspec, and it isn't enabled by default, then why is is a required dependency 🤔?

Also note that the last pathspec release was at Dec 10, 2023, and uses a MPL-2.0 license , which is incompatible with MIT I believe, but that's not a problem apparently.

@hauntsaninja
Copy link
Collaborator

Wait is there some issue with pathspec / licensing?

(We could change things around, I have some gitignore code I wrote lying around somewhere that is faster and I think slightly more correct than pathspec, I just had too much going to make it a real open source project)

@jorenham
Copy link
Contributor

Wait is there some issue with pathspec / licensing?

No sorry for the confusion, I thought so at first, but I was wrong, and they're sufficiently compatible (open-source licenses are difficult apparently)

@jorenham
Copy link
Contributor

(We could change things around, I have some gitignore code I wrote lying around somewhere that is faster and I think slightly more correct than pathspec, I just had too much going to make it a real open source project)

You're a responsible and trustworthy open source maintainer as far as I have seen, so yes, I would definitely prefer that. But I also understand the maintenance burden that comes with an open-source project (a bit too well), so you could also consider bundling it with mypy.

@jorenham
Copy link
Contributor

jorenham commented Jun 12, 2025

There's also https://github.com/mherrmann/gitignore_parser, which uses an MIT license, is very lightweight (224 LOC), has a recent release, and claims to be spec-compliant.

@kaddkaka
Copy link
Author

kaddkaka commented Jun 12, 2025

No, like most Python packages, we document our dependencies in the packaging metadata

Where can I see that?

Edit: Oh, in mypy-requirements.txt / pyproject.toml / setup.py

The reason I asked was because I had to update my nix-shell environment and our mypy nix-package. Nothing else :)

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

No branches or pull requests

4 participants