Skip to content

Commit b953f48

Browse files
bgroffbgroff
committed
Change the virtualenv section to use --system-site-packages to add the systems site-packages to the virtualenv. The --no-site-packages has been flagged as deprecated and is now the default when creating a virtualenv.
1 parent ccafe45 commit b953f48

1 file changed

Lines changed: 6 additions & 9 deletions

File tree

‎virtual_environment.rst‎

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -40,19 +40,16 @@ decision.
4040

4141
Do you want this virtualenv to use packages from your system
4242
``site-packages`` or install them in the virtualenv’s site-packages? By
43-
default, virtualenv will symlink to your system’s ``site-packages`` if
44-
you install a package in the virtualenv that is already installed on
45-
your system. If you want a totally isolated ``virtualenv`` then you’ll
46-
want to do the latter. To do this, you pass in the
47-
``-–no-site-packages`` switch when creating your virtualenv like this:
43+
default, virtualenv will not give access to the global ``site-packages``.
44+
If you want your ``virtualenv`` to have access to your systems
45+
``site-packages`` use the ``--system-site-packages`` switch when creating
46+
your virtualenv like this:
4847

4948
.. code:: python
5049
51-
$ virtualenv --no-site-packages mycoolproject
50+
$ virtualenv --system-site-packages mycoolproject
5251
53-
Now you can install any library without disturbing the global libraries
54-
or the libraries of the other environments. You can turn off the ``env``
55-
by typing:
52+
You can turn off the ``env`` by typing:
5653

5754
.. code:: python
5855

0 commit comments

Comments
 (0)