Closed ncoghlan closed 1 week ago
Local testing on the PR branch:
~/devel/venvstacks$ pipx install .
installed package venvstacks 0.1, installed using Python 3.12.6
These apps are now globally available
- venvstacks
done! โจ ๐ โจ
~/devel/venvstacks$ venvstacks --help
Usage: venvstacks [OPTIONS] COMMAND [ARGS]...
Lock, build, and publish Python virtual environment stacks.
โญโ Options โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ --help Show this message and exit. โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โญโ Commands โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ build Build (/lock/publish) Python virtual environment stacks. โ
โ local-export Export layer environments for Python virtual environment stacks. โ
โ lock Lock layer requirements for Python virtual environment stacks. โ
โ publish Publish layer archives for Python virtual environment stacks. โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
The project currently only supports execution as
python -m venvstacks
, since it seemed odd to provide a direct execution interface in a project that strips the direct execution scripts for all of the packages that it republishes.However, that rationale doesn't actually hold:
venvstacks
explicitly aims to produce the same output artifacts regardless of the Python version used to run the stack build process (so tight control of the Python version used for execution doesn't matter that much)pipx install venvstacks
,uv tool install venvstacks
, anduvx venvstacks
don't workThis issue covers:
venvstacks.cli:main
venvstacks --help
succeedsIt's OK if the help text output changes to always report
venvstacks
as the invocation method, even when invoked aspython -m venvstacks
orpython -m venvstacks.cli
(although setting it appropriately based on__main__.__spec__
would be a nicer option)