[Python-checkins] peps: wheel clarifications
daniel.holth
python-checkins at python.org
Sun Mar 10 19:33:12 CET 2013
http://hg.python.org/peps/rev/5bfc679af551
changeset: 4788:5bfc679af551
user: Daniel Holth <dholth at fastmail.fm>
date: Sun Mar 10 13:33:33 2013 -0400
summary:
wheel clarifications
files:
pep-0427.txt | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/pep-0427.txt b/pep-0427.txt
--- a/pep-0427.txt
+++ b/pep-0427.txt
@@ -96,6 +96,9 @@
point to the correct interpreter. Unix installers may need to add
the +x bit to these files if the archive was created on Windows.
+ The ``b'#!pythonw'`` convention is allowed. ``b'#!pythonw'`` indicates
+ a GUI script instead of a console script.
+
Generate script wrappers.
In wheel, scripts packaged on Unix systems will certainly not have
accompanying .exe wrappers. Windows installers may want to add them
@@ -288,6 +291,8 @@
{ "hash": "sha256=ADD-r2urObZHcxBW3Cr-vDCu5RJwT4CaRTHiFmbcIYY" }
+(The hash value is the same format used in RECORD.)
+
If RECORD.p7s is used, it must contain a detached S/MIME format signature
of RECORD.
@@ -361,6 +366,19 @@
Signed packages are only a basic building block in a secure package
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.
+
+ For example, 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.
References
==========
--
Repository URL: http://hg.python.org/peps
More information about the Python-checkins
mailing list