Skip to content

Commit

Permalink
Merge pull request #650 from ak9999/venv-section-in-current-tutorial-…
Browse files Browse the repository at this point in the history
…excludes-Windows-393

Moved language around, adding how to activate a venv on Windows
  • Loading branch information
di committed Oct 9, 2019
2 parents eff9a85 + d486aa1 commit 269d56d
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions source/tutorials/installing-packages.rst
Original file line number Diff line number Diff line change
Expand Up @@ -212,13 +212,21 @@ Using :ref:`virtualenv`:

For more information, see the `venv`_ docs or the `virtualenv <http://virtualenv.pypa.io>`_ docs.

In both of the above cases, Windows users should _not_ use the
`source` command, but should rather run the `activate` script directly
from the command shell. The use of `source` under Unix shells ensures
The use of `source` under Unix shells ensures
that the virtual environment's variables are set within the current
shell, and not in a subprocess (which then disappears, having no
useful effect).

In both of the above cases, Windows users should _not_ use the
`source` command, but should rather run the `activate` script directly
from the command shell like so:

::

<DIR>\Scripts\activate



Managing multiple virtual environments directly can become tedious, so the
:ref:`dependency management tutorial <managing-dependencies>` introduces a
higher level tool, :ref:`Pipenv`, that automatically manages a separate
Expand Down

0 comments on commit 269d56d

Please sign in to comment.