-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
pip install --no-binary
fails on Python 3.7
#392
Comments
Thanks for reporting this issue. I encountered something similar when attempting to add a dependency to For what it's worth, I don't get a recursion error as reported. Instead, I get a "LookupError":
|
You are right, I was a bit careless to call it a "recursion error". I agree that the real issue is deeper. My PR only presents a workaround. I'm not sure if that is acceptable. |
I'm struggling with what to do here. On one hand, the issue is rooted in the build dependencies ( On the other hand, this issue is currently very isolated and it's plausible it will just go away when support for Python 3.7 is dropped. In that case, the proposed workaround is a pragmatic solution. The current stance of the PyPA (from pypa/packaging-problems#342) is that |
The issue popped up in a test case in poetry-core, which is a PEP 517 build backend. Unfortunately, I'm not familiar enough with the background to say if, let alone why, this is relevant to us. I pinged a more experienced maintainer who will hopefully be able to provide some details. |
I don't believe this issue is actionable here, so I'm closing it. Happy to revisit if there's something that importlib_metadata can do. |
Nothing changed. On python 3.7 it is impossible to install importlib-metadata with --no-binary flag
|
When running
pip install --no-binary :all: importlib-metadata
or evenpip install --no-binary importlib-metadata importlib-metadata
on Python 3.7, building fails due to a recursion error. That's because the latestsetuptools_scm
version introduced a dependency onimportlib-metadata
forpython_version < "3.8"
.Maybe,
build-system requires
should be changed to require an oldersetuptools_scm
version forpython_version < "3.8"
?The text was updated successfully, but these errors were encountered: