v0.20.0

• Do not change the working directory when creating a virtual environment. This makes combining dmenv and pyenv much easier.
• Add dmenv create command to create an empty virtual environment.

v0.19.0

• Breaking: the --system-site-packages option must be passed before any subcommand, and the path of the virtual environment has changed:

<= 0.18:

$ dmenv install --system-site-packages
# virtual environment created in .venv/dev/3.7/

>= 0.19:

$ dmenv --system-site-packages install
# virtual environment created in .venv/dev-system/3.7/

• Fix #110: dmenv tidy now works even from an activated virtual environment.

v0.18.0

• Add a tidy command, to re-generate locks from a clean virtualenv.
• Switch to GitHub Actions for CI and deployment

v0.17.0

• Add a process-scripts command, to generate scripts in DMENV_SCRIPTS_PATH.

v0.16.2

• Fix regression: dmenv init could only be used with the --project option
• Improve error messages when setup.py or requirements.lock is not found
• Improve error handling when parsing output from info.py
• Fix message when using dmenv --production install

v0.16.1

• Fix regression that caused parsing output of dmenv show commands to stop working

v0.16.0

• Fix #94: Look for setup.py in the parent directories when trying to resolve the project path.

v0.15.0

• When foo.py is present at the root of the project, you can us dmenv run foo.py directly instead of
  the more awkward dmenv run -- python foo.py Fix #90

v0.14.3

• Fix syntax of generated setup.py (#86)
• Fix regression: keep the top comment when running bump-in-lock

v0.14.2

• Restore generation of precompiled binaries from travis.