Repository navigation
v0.8.1
Added
- Overlay commands get a launcher on
PATH: each top-levelbin/<name>.py, and
each[scripts]entry inoverlay.toml(name = "path"adds or replaces one,
name = falseopts abin/<name>.pyout). The launchers live in the agents'
venv, in<venv>/overlays/:<name>.exeon Windows, made with distlib's
ScriptMakerso no command interpreter parses the arguments, and a/bin/sh
script elsewhere. They run the script through$<NAME>_OVERLAY_ROOTwhen they
run, so only a new interpreter needs them made again.initandoverlays add/
sync/removekeep them current and delete those no overlay has; two
overlays with one script name is an error naming both. dotagents envputs the launcher directory of the venvAGENTS_PYTHONnames
first onPATH, ahead of the levels'bindirs, and takes any other venv's
off it.- A project gets its own venv when one of its overlays has scripts.
- New dependency:
distlib>=0.4.0,<0.5, vendored in the.pyz.
Full Changelog: v0.8.0...v0.8.1