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

Improve PEP 427 FAQ formatting

This commit is contained in:
Nick Coghlan 2014-01-29 23:50:14 +10:00
parent dc696d75e9
commit 4e4c0e8fc9
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pep-0427.txt
View File

@ -339,7 +339,10 @@ Comparison to .egg
FAQ
===
Wheel defines a .data directory. Should I put all my data there?
-----------------------------------------------------------------
This specification does not have an opinion on how you should organize
your code. The .data directory is just a place for any files that are
not normally installed inside ``site-packages`` or on the PYTHONPATH.
@ -347,26 +350,38 @@ Wheel defines a .data directory. Should I put all my data there?
resource)`` even though *those* files will usually not be distributed
in *wheel's* ``.data`` directory.
Why does wheel include attached signatures?
-------------------------------------------
Attached signatures are more convenient than detached signatures
because they travel with the archive. Since only the individual files
are signed, the archive can be recompressed without invalidating
the signature or individual files can be verified without having
to download the whole archive.
Why does wheel allow JWS signatures?
------------------------------------
The JOSE specifications of which JWS is a part are designed to be easy
to implement, a feature that is also one of wheel's primary design
goals. JWS yields a useful, concise pure-Python implementation.
Why does wheel also allow S/MIME signatures?
--------------------------------------------
S/MIME signatures are allowed for users who need or want to use
existing public key infrastructure with wheel.
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 "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
@ -381,7 +396,10 @@ What's the deal with "purelib" vs. "platlib"?
depending on whether it is pure Python or not and those files should
be at the root with the appropriate setting given for "Root-is-purelib".
Is it possible to import Python code directly from a wheel file?
----------------------------------------------------------------
Yes, the wheel format is deliberately designed to be compatible with
Python's support for importing from zip files, ensuring that it
provides a superset of the functionality provided by the preceding