-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Specifying --use-pep517 to a non-pyproject.toml project should populate build requirements #9523
Comments
I can replicate the issue in isolation using this local package:
|
Yes, and |
I edited the title to reflect my understanding to the root cause. |
FWIW, this is where the I tried adding |
@SpecLad I think that’s on the right track. Feel free to submit a PR and a test case and we can go from there. |
Environment
Description
Attempting to download a project that depends on
termcolor~=1.1.0
fails to build the metadata for termcolor if setuptools isn't implicitly installed, even with pep517 enabled.In order to wean myself from implicit setuptools, I've left setuptools uninstalled from my environment, and instead rely on passing
--use-pep517
to invoke the "fallback to setuptools" behavior for packages not supplying pyproject.toml. Downloading justtermcolor
by itself works without error, but attempting to download a project that depends on termcolor (such as tensorflow) will fail to build the metadata for termcolor. It seems that the pep517 fallback to setuptools behavior doesn't take effect in the download command.Expected behavior
Passing
--use-pep517
to pip should enable the fallback to setuptools behavior (and make it available for a project if the build dependencies aren't specified in pyproject.toml).How to Reproduce
The text was updated successfully, but these errors were encountered: