[Python-checkins] peps: Clarify purelib vs platlib in PEP 427

[nick.coghlan]

http://hg.python.org/peps/rev/8a53c2356865
changeset:   5363:8a53c2356865
user:        Nick Coghlan <ncoghlan at gmail.com>
date:        Tue Jan 28 23:21:43 2014 +1000
summary:
  Clarify purelib vs platlib in PEP 427

files:
  pep-0427.txt |  11 ++++++-----
  1 files changed, 6 insertions(+), 5 deletions(-)


diff --git a/pep-0427.txt b/pep-0427.txt
--- a/pep-0427.txt
+++ b/pep-0427.txt
@@ -367,18 +367,19 @@
     update system.  Wheel only provides the building block.
 
 What's the deal with "purelib" vs. "platlib"?
-    Wheel preserves the historic "purelib" vs. "platlib" distinction
-    even though both map to the same install location in any system the
-    author could find.
+    Wheel preserves the "purelib" vs. "platlib" distinction, which is
+    significant on some platforms. For example, Fedora installs pure
+    Python packages to '/usr/lib/pythonX.Y/site-packages' and platform
+    dependent packages to '/usr/lib64/pythonX.Y/site-packages'.
 
-    For example, a wheel with "Root-Is-Purelib: false" with all its files
+    A wheel with "Root-Is-Purelib: false" with all its files
     in ``{name}-{version}.data/purelib`` is equivalent to a wheel with
     "Root-Is-Purelib: true" with those same files in the root, and it
     is legal to have files in both the "purelib" and "platlib" categories.
 
     In practice a wheel should have only one of "purelib" or "platlib"
     depending on whether it is pure Python or not and those files should
-    be at the root.
+    be at the root with the appropriate setting given for "Root-is-purelib".
 
 References
 ==========

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