alternative automatic installation of poetry

[houbie]

Two months ago, our team switched from Java and Javascript to python. We love the language, but had some hard times setting up our dev environment, i.e. some devs had troubles installing poetry on their machines.

In Java land, gradle introduced the gradle wrapper scripts; *nix and windows gradlew scripts that download (and cache) the desired gradle version on the fly when running a command.

Python Wraptor tries to achieve the same for Python based tools.
You just add the shell scripts to your repo, configure your tools in pyproject.toml and prefix all commands with pw, f.e. ./pw poetry install.

On the first invocation it creates a tool/version specific virtual environment in ~/.python-wraptor/venvs and delegates the command.
When multiple projects use the same version of a tool (f.e. poetry 1.1.7), it only gets installed once.

These wrapper scripts become invaluable once poetry 2.0 gets out: devs will work on different projects requiring different versions of poetry and can't rely anymore on the single global poetry install (in Java land we cursed a lot when Maven 3 was released, until Maven also introduced the mvnw scripts).

Check out the wrapped-pi example project and please share your thoughts...