-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Only allow the finder to use wheels as build reqs #4987
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
Conversation
Shouldn't the message read "This version of pip does not implement PEP 518", not 516? |
@benoit-pierre Yes. |
Um, PEP 517. 516 is the rejected version of build system abstraction, 517 is the accepted build system abstraction, and 518 is |
Having said that, the message is not from this PR (which looks fine to me) but from somewhere else. As far as I can see, though, the message is confused - we're not trying to build a wheel without setuptools, we're simply trying to install a build-time dependency of Regardless, though, that's a cosmetic issue. I'm happy with this PR as a temporary fix for PEP 518 support to require that build dependencies have to be wheels for now. (Although travis isn't - looks like there are tests that need fixing...) |
I'll make a separate PR for improving the message. I'll look into the test failure in ~12 hours. It's probably because something in the test harness is using an sdist build dependency. |
Additional investigation needed: can arbitrary URLs be a build-dependency and pip still installs it? |
Another idea: Disabling all of the current PEP 518 stuff with a flag, just in case there's some security hole in there? This has the nice advantage of telling us the exact branches that need to be changed post 10.0. |
Actually, we are. pip-forkbomb-test doesn't list setuptools in |
Yes. (apologies for the terse replies, I'm in the middle of something else) |
Fixed by switching to simplewheel from simple in the test. |
Excellent work, @pradyunsg! |
When merging this PR, please use plain merge instead of squash/rebase merges since I have another branch sitting on top of this one now. |
@pypa/pip-committers Is there anything else we want to do here before we can merge? |
Not that I know of |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #4983
See also #4802 (comment)
The message isn't ideal but I think that is for a separate PR.