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

Document PEP517 difference #4480

Merged
merged 2 commits into from
Jun 24, 2024
Merged

Conversation

covracer
Copy link
Contributor

Summary

PEP 517 build isolation #843 has not yet been mentioned in the PIP compatibility documentation. Add a section for it.

Test Plan

Visual inspection only

Open Questions

in most cases, swapping out pip install for uv pip install should "just work".

In the first non-trivial case I tried, it worked for a short time and then started failing. Is there any data out there on how many top 100 or top 1000 packages work with PEP 517 build isolation?

How can someone specify --no-build-isolation for just one package/line in requirements.txt?

@charliermarsh
Copy link
Member

Good question... My guess is that ~all of the top 100 and top 1000 packages work with PEP 517 build isolation, though I haven't tried it.

@charliermarsh charliermarsh self-assigned this Jun 24, 2024
@charliermarsh charliermarsh added the documentation Improvements or additions to documentation label Jun 24, 2024
@charliermarsh charliermarsh enabled auto-merge (squash) June 24, 2024 20:32
@charliermarsh charliermarsh merged commit 01515c1 into astral-sh:main Jun 24, 2024
38 checks passed
@covracer covracer deleted the pep517-differnce branch June 25, 2024 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants