[Python-checkins] peps: Edit include files section of PEP 405.

[vinay.sajip]

http://hg.python.org/peps/rev/adbc23f61cd0
changeset:   4432:adbc23f61cd0
parent:      4428:f2500baa8a51
user:        Carl Meyer <carl at oddbird.net>
date:        Thu May 24 14:18:29 2012 -0600
summary:
  Edit include files section of PEP 405.

files:
  pep-0405.txt |  13 ++++++-------
  1 files changed, 6 insertions(+), 7 deletions(-)


diff --git a/pep-0405.txt b/pep-0405.txt
--- a/pep-0405.txt
+++ b/pep-0405.txt
@@ -299,19 +299,18 @@
 
 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
 ---

-- 
Repository URL: http://hg.python.org/peps