From 8ac7d6ffef4b0d683b8781aaac81e9c3aac6880c Mon Sep 17 00:00:00 2001 From: Niko Pasanen Date: Tue, 29 Dec 2020 17:03:09 +0200 Subject: [PATCH] notes for 0.5.0 --- docs/venvlink-and-pew.md | 3 ++- docs/venvlink-and-pipenv.md | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/venvlink-and-pew.md b/docs/venvlink-and-pew.md index ddd62a0..aac6897 100644 --- a/docs/venvlink-and-pew.md +++ b/docs/venvlink-and-pew.md @@ -95,4 +95,5 @@ Type "help", "copyright", "credits" or "license" for more information. - When using `activate` script created with `venvlink` (or python `venv`), the name of the active virtual environment is shown in parenthesis at the left side of the shell prompt. - When using `pew workon`, the virtual environment can be activated from anywhere using the ***name*** of the virtual environment. When using `venvlink`, the virtual environment can be activated using the ***`activate` script*** which is located the project folder (can also be called anywhere). - When creating virtual environments, one must be in a project folder, to create a virtual environment with `venvlink`, but you can create virtual environment anywhere using `pew`. -- The activate script using `venvlink` will colorize the virtual environment name, if using Powershell. \ No newline at end of file +- The activate script using `venvlink` will colorize the virtual environment name, if using Powershell. +- `venvlink` (0.5.0+) has support for automatically activating and deactivating virtual environments in Powershell using [venvlink-autoenv](https://github.com/np-8/venvlink-autoenv-powershell). \ No newline at end of file diff --git a/docs/venvlink-and-pipenv.md b/docs/venvlink-and-pipenv.md index 9d312d9..254e4bf 100644 --- a/docs/venvlink-and-pipenv.md +++ b/docs/venvlink-and-pipenv.md @@ -25,7 +25,7 @@ - With `venvlink`, one would activate the virtual environment using the `activate` script ("link") located in the project folder. The cwd can be anything when the `activate` script is ran. - With `venvlink` it is also possible to run the python executable directly with `//Scipts/python.exe ...`, if needed (as with when using `venv` without `venvlink`) - It is also possible to use [`pew` with venvlink](venvlink-and-pew.md). (and activate virtual environments using `pew workon myproject`) - + - `venvlink` (0.5.0+) has support for automatically activating and deactivating virtual environments in Powershell using [venvlink-autoenv](https://github.com/np-8/venvlink-autoenv-powershell). ## Changing virtual environments