Skip to content
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: Use build isolation only for "modern" sdists #5049

Closed
pradyunsg opened this issue Mar 2, 2018 · 6 comments
Closed

PEP 518: Use build isolation only for "modern" sdists #5049

pradyunsg opened this issue Mar 2, 2018 · 6 comments
Labels
auto-locked Outdated issues that have been locked by automation type: maintenance Related to Development and Maintenance Processes
Milestone

Comments

@pradyunsg
Copy link
Member

Currently, the PEP 518 support in pip does every wheel build in isolation -- at least as per my understanding -- and this is not correct. This would break a lot of existing packages and we don't want to do that.

The correct behaviour here would be to branch on the "legacy" sdists to run as we did with pip 9 and to run "modern" sdists through the isolation currently in pip master.

I realized this thanks to #5033.

@pradyunsg pradyunsg added !release blocker Hold a release until this is resolved type: maintenance Related to Development and Maintenance Processes labels Mar 2, 2018
@pradyunsg pradyunsg added this to the 10.0 milestone Mar 2, 2018
@ghost
Copy link

ghost commented Mar 2, 2018

This is not correct, and in addition, not related to gh-5033. This issue should be closed.

@ghost
Copy link

ghost commented Mar 2, 2018

if not isolate:
self.req.build_env = NoOpBuildEnvironment(no_clean=False)

@pradyunsg
Copy link
Member Author

Ah right. I got misdirected by:

isolate=True)

It is indeed unrelated to #5033. I just remembered because of it. =)

@ghost
Copy link

ghost commented Mar 2, 2018

Actually, that kwarg should be removed.

@pradyunsg
Copy link
Member Author

Yep. I agree. =)

@lock
Copy link

lock bot commented Jun 2, 2019

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.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

No branches or pull requests

1 participant