Skip to content

Conversation

@rpanderson
Copy link
Owner

Demonstration of how to use aliases to derive requirements files as alluded to in #1.

  • requirements/default.txt contains ., referring to install_requires in setup.cfg.
  • requirements/<some_extra>.txt contains .[<some_extra>], referring to install_requires and the relevant values in extras_require in setup.cfg.

Development requirements can then be installed using, e.g.:

$ pip install -r requirements/development.txt

Although I'm not sure how that's any different to:

$ pip install -e .[development]

Notes

  • Extras can be combined, e.g. .[development,docs]
  • Unlike explicitly created requirements files, all of the extras include the base requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants