Installation¶
wreck is available at PyPi wreck,
and can be installed from pip or source as follows.
python -m pip install wreck
git clone https://github.com/msftcangoblowm/wreck
cd wreck
python -m venv .venv
. .venv/bin/activate
python -m pip install -r requirements/kit.lock -r requirements/prod.lock
python -m build
python -m pip install --force-reinstall --no-deps dist/wreck-0.1.0-py3-none-any.whl
Release tarball and wheel that are uploaded to pypi, is created by Github CI/CD . Not the author.
How to setup pyenv is explained in Contributing
Configuration¶
In pyproject.toml, for each venv, add a [[tool.venv]] section.
Sample venv for production and dev tools.
[[tool.wreck.venvs]]
venv_base_path = '.venv'
reqs = [
'requirements/pip',
'requirements/pip-tools',
'requirements/prod',
'requirements/dev',
'requirements/manage',
'requirements/kit',
'requirements/mypy',
'requirements/tox',
]
Sample venv for docs
[[tool.wreck.venvs]]
venv_base_path = '.doc/.venv'
reqs = [
'docs/requirements',
'docs/pip-tools',
]
These are top most level requirement files without last suffix.
The additional requirements are for use by tox and CI/CD workflows.
use posix relative paths. Yes! Windows users too
assumes venvs are within the package base folder
requirements and constraints files are not required to be in a subfolder, however it’s highly encouraged