From fe8f90aa3ca3f277cac634cdb96b829039225c6b Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Thu, 9 Aug 2018 08:10:27 -0700 Subject: [PATCH] bpo-34324: Doc README wrong directory name for venv (GH-8650) MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit In the documentation, the `env` directory is specified when we execute the `make venv` command. But in the code, `make venv` will create the virtualenv inside the `venv` directory (defined by `VENVDIR`) (cherry picked from commit 599bfa18f8ebcb23af300b6855934048c3c64e7d) Co-authored-by: Stéphane Wirtel --- Doc/README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/README.rst b/Doc/README.rst index a29d1f3a708a..d7bcc5ba7919 100644 --- a/Doc/README.rst +++ b/Doc/README.rst @@ -33,7 +33,7 @@ To get started on UNIX, you can create a virtual environment with the command :: make venv That will install all the tools necessary to build the documentation. Assuming -the virtual environment was created in the ``env`` directory (the default; +the virtual environment was created in the ``venv`` directory (the default; configurable with the VENVDIR variable), you can run the following command to build the HTML output files:: -- 2.47.3