iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Edit include files section of PEP 405.

This commit is contained in:
Carl Meyer 2012-05-24 14:18:29 -06:00
parent 3595fae7e4
commit 2a01d82b09
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pep-0405.txt
View File

@ -299,19 +299,18 @@ standard abstraction for a site-specific include directory.
This PEP proposes a slightly different approach, though one with
essentially the same effect and the same set of advantages and
disadvantages. Rather than symlinking or copying include files into
the venv, we simply modify the sysconfig schemes so that header files
are always looked for relative to ``base_prefix`` rather than
``prefix``. (We also create an ``include/`` directory within the venv
disadvantages. Rather than symlinking or copying include files into the
venv, we simply modify the sysconfig schemes so that header files are
always looked for relative to ``base_prefix`` rather than
``prefix``. (We also create an ``include/`` directory within the venv,
so installers have somewhere to put include files installed within the
env).
Better handling of include files in distutils/packaging and, by
extension, pyvenv, is an area that may deserve its own future PEP. For
now, we propose that the behavior of virtualenv has thus far proved
itself to be at least "good enough" in practice.
[Open question: should pyvenv instead simply copy the behavior of
virtualenv entirely, to avoid introducing unexpected new issues here?]
API
---