Browse Source

Improve wording about virtual environment activation

Clarify that once a virtual environment is activated,
newly installed packages become available immediately
and re-activating the environment is usually unnecessary.
pull/15107/head
24ds1000054-code 4 months ago
committed by GitHub
parent
commit
73cc45b87b
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/en/docs/virtual-environments.md

2
docs/en/docs/virtual-environments.md

@ -164,7 +164,7 @@ $ source .venv/Scripts/activate
/// tip /// tip
Every time you install a **new package** in that environment, **activate** the environment again. Once a virtual environment is activated, newly installed **packages** become available immediately, so re-activating the environment is usually not necessary.
This makes sure that if you use a **terminal (<abbr title="command line interface">CLI</abbr>) program** installed by that package, you use the one from your virtual environment and not any other that could be installed globally, probably with a different version than what you need. This makes sure that if you use a **terminal (<abbr title="command line interface">CLI</abbr>) program** installed by that package, you use the one from your virtual environment and not any other that could be installed globally, probably with a different version than what you need.

Loading…
Cancel
Save