Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add pip-tools related-files to the project
We have to use a `requirements.in` just to proxy `setup.cfg`, since an error occurs when we rely on the implicit dependency (ref: jazzband/pip-tools#572). This way abstracted requirements are expressed via `setup.cfg` while concrete dependencies are expressed via `requirements.txt`. Basic workflow: - Add abstract dependencies to `setup.cfg` - Proxy `setup.cfg` using `requirements.in` - Write dev dependencies to `dev-requirements.in` - Use `pip-compile --output-file (dev-)requirements.txt (dev-)requirements.in` to compile the concrete dependencies - Add the `requirements.{in,txt}` files to source control for repeatable installations: https://caremad.io/posts/2013/07/setup-vs-requirement/ - Use `pip-sync dev-requirements.txt requirements.txt` to install the packages into the current virtualenv - Run commands normally inside the current virtualenv (e.g. `tox`) - Don't expose test requirements directly to pip-tools. Instead, just rely on tox/pytest-runner to install them inside the test venv.
- Loading branch information