- veman now reads the environment variable
VEMAN_ENV_DIR
which can be used to override which directory is used for managed environments. - The symlinks
python
andpython3
in an environments bin folder were not replaced by default by the venv module when upgrading a venv, veman now delete the symlinks to ensure that new symlinks are created during an upgrade. - New option
--all
to the commandveman upgrade
to upgrade all existing venvs. The--all
option can be used with or without existing options to the upgrade command. - New option
--context
to print system environment context (mainly used for debugging & testing).
- Activated support for FreeBSD with Bash (tested on FreeBSD and GhostBSD)
- New option
--prompt <prompt-prefix>
forcreate
command to set shell prompt prefix - New option
--system-site-packages
forcreate
command to enable access to system site-packages in venv - New option
--without-pip
forcreate
command to create venv without installing pip - Minor bug fix: Running the
upgrade
command on a non-existing venv would create a new venv - Minor bug fix: Running
create -a <venv_name>
with a venv_name that already exists and choosing not to overwrite the existing venv would activate the existing venv
- Minor changes to fix PyPi issue
- No functional changes to veman in this release
- New command
upgrade
to upgrade core dependencies, python version and veman scripts in venv - New option
--verbose
forhistory
command - Check for compatible Python version
- Documentation now available at https://tranbom.io/veman/
- New argument
-a
or--activate
for the create command to activate a venv after creationveman create -a testenv
- New command
history
to print the bash history for a venv, or for all venvs with--all
veman temp
can now create multiple temporary environments simultaneously- veman now sources
/etc/profile
and~/.bash_profile
on macOS - Customisations to the veman_activate bash script for macOS
- veman now maintains separate bash history for each venv, the history is automatically restored when a virtual environment is activated.
veman temp
will create a temporary venv which will be deleted immediately on deactivation.veman --version
will print current version.
- Command
create
no longer works inside an activated virtual environment. - Activated support for macOS with Bash (limitation: veman currently only sources ~/.bashrc)
- Commands
create
,activate
,list
&delete
implemented