Oops, we're not copying includes into the venv.
This commit is contained in:
parent
dd516e8d3b
commit
491a834fc5
21
pep-0405.txt
21
pep-0405.txt
|
@ -242,12 +242,11 @@ Copies versus symlinks
|
|||
----------------------
|
||||
|
||||
The technique in this PEP works equally well in general with a copied
|
||||
or symlinked Python binary (and other needed DLLs and the ``Include``
|
||||
directory on Windows). Symlinking is preferable where possible,
|
||||
because in the case of an upgrade to the underlying Python
|
||||
installation, a Python executable copied in a venv might become
|
||||
out-of-sync with the installed standard library and require manual
|
||||
upgrade.
|
||||
or symlinked Python binary (and other needed DLLs on Windows).
|
||||
Symlinking is preferable where possible, because in the case of an
|
||||
upgrade to the underlying Python installation, a Python executable
|
||||
copied in a venv might become out-of-sync with the installed standard
|
||||
library and require manual upgrade.
|
||||
|
||||
There are some cross-platform difficulties with symlinks:
|
||||
|
||||
|
@ -268,11 +267,11 @@ option has no effect on OS X framework builds, since symlinking can
|
|||
never work there, and has no advantages).
|
||||
|
||||
On Windows, if ``--symlink`` is not used, this means that if the
|
||||
underlying Python installation is upgraded, the Python binary, DLLs,
|
||||
and include files in the venv should be updated, or there could be
|
||||
issues of mismatch with the upgraded standard library. The pyvenv
|
||||
script accepts a ``--upgrade`` option for easily performing this
|
||||
upgrade on an existing venv.
|
||||
underlying Python installation is upgraded, the Python binary and DLLs
|
||||
in the venv should be updated, or there could be issues of mismatch
|
||||
with the upgraded standard library. The pyvenv script accepts a
|
||||
``--upgrade`` option for easily performing this upgrade on an existing
|
||||
venv.
|
||||
|
||||
|
||||
Include files
|
||||
|
|
Loading…
Reference in New Issue