From: mkkot Date: Fri, 14 Dec 2018 20:28:52 +0000 (+0100) Subject: bpo-35450: reflect in docs that venv module is not always creating a … (GH-11144) X-Git-Tag: v3.8.0a1~273 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f5107dfd42121ef40b13eb678705802f0ff02cf9;p=thirdparty%2FPython%2Fcpython.git bpo-35450: reflect in docs that venv module is not always creating a … (GH-11144) …copy of python binary https://bugs.python.org/issue35450 --- diff --git a/Doc/using/venv-create.inc b/Doc/using/venv-create.inc index 45abd59d1868..ba5096abd370 100644 --- a/Doc/using/venv-create.inc +++ b/Doc/using/venv-create.inc @@ -7,9 +7,10 @@ Running this command creates the target directory (creating any parent directories that don't exist already) and places a ``pyvenv.cfg`` file in it with a ``home`` key pointing to the Python installation from which the command was run. It also creates a ``bin`` (or ``Scripts`` on Windows) subdirectory -containing a copy of the ``python`` binary (or binaries, in the case of -Windows). It also creates an (initially empty) ``lib/pythonX.Y/site-packages`` -subdirectory (on Windows, this is ``Lib\site-packages``). If an existing +containing a copy/symlink of the Python binary/binaries (as appropriate for the +platform or arguments used at environment creation time). It also creates an +(initially empty) ``lib/pythonX.Y/site-packages`` subdirectory +(on Windows, this is ``Lib\site-packages``). If an existing directory is specified, it will be re-used. .. deprecated:: 3.6