gh-109414: Add some basic information about venvs in the introduction. (GH-109440)

Co-authored-by: Victor Stinner <vstinner@python.org>
This commit is contained in:
Vinay Sajip 2023-09-16 09:49:02 +01:00 committed by GitHub
parent 0b38ce440b
commit a6846d45ff
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -30,6 +30,25 @@ When used from within a virtual environment, common installation tools such as
`pip`_ will install Python packages into a virtual environment
without needing to be told to do so explicitly.
A virtual environment is (amongst other things):
* Used to contain a specific Python interpreter and software libraries and
binaries which are needed to support a project (library or application). These
are by default isolated from software in other virtual environments and Python
interpreters and libraries installed in the operating system.
* Contained in a directory, conventionally either named ``venv`` or ``.venv`` in
the project directory, or under a container directory for lots of virtual
environments, such as ``~/.virtualenvs``.
* Not checked into source control systems such as Git.
* Considered as disposable -- it should be simple to delete and recreate it from
scratch. You don't place any project code in the environment
* Not considered as movable or copyable -- you just recreate the same
environment in the target location.
See :pep:`405` for more background on Python virtual environments.
.. seealso::