Use pyproject.toml to store Python dependencies instead of requirements.in
#211
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Store requirements and setup dev requirements as optional dependencies
There are now two requirements files: - requirements.txt which only contains runtime dependencies. - dev-requirements.txt which contains runtime dependencies and local developer tools like black and ruff.
This is replaced with pyproject.toml.
lopopolo
added
A-deps
lopopolo
force-pushed
the
lopopolo/pip-tools-pyproject.toml
branch
from
ca59eb2 to
8ccde5d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change allows for splitting out dev dependencies (black, mypy, ruff) into an "extra" set of optional dependencies which don't get installed during runtime during codesigning in the nightly job.