diff options
author | Stéphane Wirtel <stephane@wirtel.be> | 2018-08-09 15:05:31 (GMT) |
---|---|---|
committer | Mariatta <Mariatta@users.noreply.github.com> | 2018-08-09 15:05:31 (GMT) |
commit | 599bfa18f8ebcb23af300b6855934048c3c64e7d (patch) | |
tree | 14e5ddb39ad215461d267238fd54db4ade140c1f /Doc | |
parent | cca4eec3c0a67cbfeaf09182ea6c097a94891ff6 (diff) | |
download | cpython-599bfa18f8ebcb23af300b6855934048c3c64e7d.zip cpython-599bfa18f8ebcb23af300b6855934048c3c64e7d.tar.gz cpython-599bfa18f8ebcb23af300b6855934048c3c64e7d.tar.bz2 |
bpo-34324: Doc README wrong directory name for venv (GH-8650)
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`)
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/README.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/README.rst b/Doc/README.rst index b349160..31f8a8b 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:: |