-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
No, like most Python packages, we document our dependencies in the packaging metadata |
I believe that @kaddkaka wants to know why mypy now requires |
Linking #18696 for context |
The Also note that the last |
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) |
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) |
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. |
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. |
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 :) |
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?The text was updated successfully, but these errors were encountered: