[Python-checkins] peps: Improve PEP 427 FAQ formatting

[nick.coghlan]

http://hg.python.org/peps/rev/c1118d37ed3a
changeset:   5366:c1118d37ed3a
user:        Nick Coghlan <ncoghlan at gmail.com>
date:        Wed Jan 29 23:50:14 2014 +1000
summary:
  Improve PEP 427 FAQ formatting

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
@@ -339,7 +339,10 @@
 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 @@
     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 @@
     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

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