Requirements files derived from setuptools install_requires extras_requires #4
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.
Demonstration of how to use aliases to derive requirements files as alluded to in #1.
requirements/default.txt
contains.
, referring toinstall_requires
insetup.cfg
.requirements/<some_extra>.txt
contains.[<some_extra>]
, referring toinstall_requires
and the relevant values inextras_require
insetup.cfg
.Development requirements can then be installed using, e.g.:
Although I'm not sure how that's any different to:
Notes
.[development,docs]