-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
6.0.0 has an undeclared dependency on importlib-metadata at python 3.6 #1352
Comments
I have the same issue on my 3.6 projects when they pip-compile. But, if the import is coming from within pip, wouldn't this be pip's fault, for not depending on this properly when it vendored pep517? edit: it looks like pep517 requires importlib_metadata for python<3.8 |
pip is not broken, and I expect that pip maintainers would say: if pip-tools chooses to rely on the internals of pip, then it is pip-tools problem to make that work. (I don't know why pip-tools doesn't depend on pep517 directly, probably there's a good reason) |
I see there was discussion on whether or not to use pip's private vendored copy of pep517 at #1311 (comment) FWIW I'm on team prefer-public-APIs, and I think this issue supports that. But, maintainer's choice! |
Hello @dimbleby, Thanks for the report! Huh, that was overlooked somehow. The fix is on the way. |
I have the same issue, it breaks my 3.6 and 3.7 builds. The patch 6.0.1 is not on PyPI yet, guess I will have to roll back to the previous version for now? |
FYI I'm attempting to get the 6.0.1 fix out right now, but the GH Actions seems to have a rather long queue time and having issues starting the job. |
There we go, |
Amazing! Thanks @vphilippon |
pip-compile from pip-tools 6.0 doesn't work at python 3.6, throws an error about failing to find importlib.metadata
Environment Versions
pip-tools 6.0.0, python 3.6.8 are the important ones
Steps to replicate
Expected result
Actual result
The text was updated successfully, but these errors were encountered: