[3.13] Improved venv docs to indicate that isolation is the default. (GH-136698)...

(cherry picked from commit 8e2f4b448380b4c835442534d566618f06e32573)

diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst
index 1f9a5e6e06c823917e87a0ba782b0e83ca27ef9e..224f497dde7c6522670725ebeeffbdc79a4182eb 100644 (file)
--- a/Doc/library/venv.rst
+++ b/Doc/library/venv.rst
@@ -22,9 +22,9 @@ The :mod:`!venv` module supports creating lightweight "virtual environments",
 each with their own independent set of Python packages installed in
 their :mod:`site` directories.
 A virtual environment is created on top of an existing
-Python installation, known as the virtual environment's "base" Python, and may
-optionally be isolated from the packages in the base environment,
-so only those explicitly installed in the virtual environment are available.
+Python installation, known as the virtual environment's "base" Python, and by
+default is isolated from the packages in the base environment, so
+that only those explicitly installed in the virtual environment are available.
 
 When used from within a virtual environment, common installation tools such as
 :pypi:`pip` will install Python packages into a virtual environment