Releases · dmerejkowsky/dmenv

dmenv install and dmenv lock commands learned the --system-site-packages option to create virtual environments that have access to packages installed globally on the system.

Allow skipping dev dependencies

This is done with the --production flag. For instance, dmenv --production install.
dmenv --production lock will create a production.lock that contains no development dependencies.

Breaking changes

Virtualenv location has changed to allow both production and full virtual environments to coexist:

When using DMENV_VENV_OUTSIDE_PROJECT

version	location
<= 0.11	DATA_DIR/dmenv/venv/3.7.1/foo/
>= 0.12, default	DATA_DIR/dmenv/venv/dev/3.7.1/foo/
>= 0.12, with --production	DATA_DIR/dmenv/venv/prod/3.7.1/foo/

Otherwise:

version	location
<= 0.11	.venv/3.7.1/foo/
>= 0.12, default	.venv/dev/3.7.1/foo/
>= 0.12, with --production	.venv/prod/3.7.1/foo/

Migrating from 0.11

Run dmenv clean with dmenv 0.11 to clean up the deprecated location
Upgrade to dmenv 0.12
Run dmenv install to create the new virtual environment

Assets 5

01 Mar 13:42

dmerejkowsky

v0.11.1

b59bee9

v0.11.1

Fix metadata on crates.io to include new tagline.

Assets 5

20 Feb 10:55

dmerejkowsky

v0.11.0

14a8f36

v0.11.0

Add dmenv show:bin_path to show the path of the virtual environment binaries.

Breaking changes

Fix #31: make sure the wheel package gets frozen when running dmenv lock. Note: this also causes other packages like setuptools and pip itself to get frozen. As a consequence dmenv install no longer upgrades pip automatically, and so the --no-upgrade-pip option is gone.