-
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
PEP-518 support is broken #5188
Comments
Feel free to go ahead and open up a PR for this. |
Sure, but are we in agreement over the changes? Particularly: checking for both setuptools and wheel, since we need both. I ran the testsuite locally, and 3 tests fail (as expected):
IHMO those don't make sense anymore and should just be removed, agreed? |
The testsuite is also clearly missing a test to ensure all commands are run with the build environment enabled. |
Yes. Minor nit about the message -- if only one is missing, the message shouldn't say "those".
Yes.
Yes. Thanks for trying out the PEP 518 support -- and actually figuring out it's broken. :) |
How about |
Or the message could be changed to show the missing requirements. |
Showing missing requirements. |
I was under the impression that build isolation could only disabled with |
When there's no |
You're too nice... |
Uhm... Okay? That's very vague. I'm not even sure if that's a complement or
sarcastic.
…On Sun, 8 Apr 2018, 11:59 Benoit Pierre, ***@***.***> wrote:
You're too nice...
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#5188 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADH7SQo2j_VfxL1akAW63WfkKEUQVjozks5tma4xgaJpZM4TLY9u>
.
|
It is sarcastic. |
Sorry that you felt that way -- I'm being terse because I'm in the middle of something else right now. :/ |
The |
Oh. Okay. Could you elaborate upon why you feel so? |
Too many codepaths, too much code. There are already several way for users to keep the current behavior: don't update, or use |
A package without PEP 518 support, should not have build isolation since that's a (big) change in behavior -- that'll break things in an unexpected way for people. It might happen that someone installs a PEP 518 package and a legacy package in the same pip run and one wants isolation while the other doesn't. This is an important case to have working for an easy transition -- hence we can't have a all-in-or-nothing approach here. I do agree there's a lot of code paths and honestly, the best way to fix that would be refactors to make life easier like #5051. |
I'd be in favour of reducing the number of code paths post-10.0, but before we consider that we would have to look at how we communicate such changes. Making everyone with an existing project, with a workflow that involves installing build requirements manually, add Also, refactorings like #5051 should be much easier post-10.0 when we've gone past the pain of pushing the message that our internals are private. |
Closing on account of #5190. |
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. |
Description:
Steps to reproduce (run from pip' source directory):
Note the 2 additional minor issues:
None
instead of the package name because it's not yet knownsetuptools
presence in the build requirements failsAdditionally, now that PEP 518 is implemented, building a wheel should be possible even if the wheel package is not installed (as long as it's in the build requirements):
Tentative patch:
The text was updated successfully, but these errors were encountered: