feat(pip-compile): Support compiling dependencies from pyproject.toml #37457
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
pip-compile
(anduv pip compile
) support compiling dependencies from pyproject.toml, but that functionality wasn't enabled in the pip-compile manager. This uses the pep621 manager'sextractPackageFile
the same way we do with the pip_setup and pip_requirements managers to enable the pip-compile maanger to handle pyproject.toml files.Context
My org has started moving more of our package configuration into pyproject.toml files. We still use setuptools for package builds though, and setuptools doesn't have a native lock file like other PEP-621 managers. We use pip-compile to generate requirements.txt files that act as lock files for our CI tests and for application deployments.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: