wreck is a dependencies manager, which is venv aware, BUT is not a venv manager nor does it put dependencies into pyproject.toml. Sticks with good ol’ requirement files.

Assumes, for each package, it’s normal to be working with several venv.

Syncs the dependencies intended for the same venv.

req fix --venv-relpath='.venv'
req fix --venv-relpath='.doc/.venv'

Across many packages, unfortunately have to resort to manually sync’ing dependencies.

Lessons learned

• have very recently ceased putting build requirements into requirement files. The build requirements’ transitive dependencies should be in the requirement files. wreck does not support this yet. i’m manually removing dependencies like: build wheel setuptools-scm (setuptools and pip already filtered out) and click.

• syncing across packages is really time consuming. Go thru this pain, then no dependency hell.

Wrote wreck cuz all the other options were combining requirements management with everything including the bathroom sink. build backends … venv management … everything goes into pyproject.toml. All these ideas seem to just compound the learning curve.

Less is more especially when it comes to learning curve.