Accept PEP 427 (wheel format)

This commit is contained in:
Nick Coghlan 2013-02-16 21:14:38 +10:00
parent 3515a9e84e
commit 8bae85b3f6
1 changed files with 26 additions and 19 deletions

View File

@ -1,16 +1,16 @@
PEP: 427
Title: The Wheel Binary Package Format 0.1
Title: The Wheel Binary Package Format 1.0
Version: $Revision$
Last-Modified: $Date$
Author: Daniel Holth <dholth@fastmail.fm>
BDFL-Delegate: Nick Coghlan <ncoghlan@gmail.com>
Discussions-To: <distutils-sig@python.org>
Status: Draft
Status: Accepted
Type: Standards Track
Content-Type: text/x-rst
Created: 20-Sep-2012
Post-History: 18-Oct-2012, 15-Feb-2013
Resolution: http://mail.python.org/pipermail/python-dev/2013-February/124103.html
Abstract
========
@ -26,13 +26,11 @@ may be installed by simply unpacking into site-packages with the standard
out onto their final paths at any later time.
Note
====
PEP Acceptance
==============
This draft PEP describes version 0.1 of the "wheel" format. When the PEP
is accepted, the version will be changed to 1.0. (The major version
is used to indicate potentially backwards-incompatible changes to the
format.)
This PEP was accepted, and the defined wheel version updated to 1.0, by
Nick Coghlan on 16th February, 2013 [1]_
Rationale
@ -175,25 +173,26 @@ its version, e.g. ``1.0.0``, consist of:
``#!python`` rewriting at install time. They may have any or no
extension.
#. ``{distribution}-{version}.dist-info/METADATA`` is Metadata version 1.1
or greater (PEP 314, PEP 345, PEP 426) format metadata.
or greater format metadata.
#. ``{distribution}-{version}.dist-info/WHEEL`` is metadata about the archive
itself in the same basic key: value format::
Wheel-Version: 0.1
Generator: bdist_wheel 0.7
Wheel-Version: 1.0
Generator: bdist_wheel 1.0
Root-Is-Purelib: true
Tag: py2-none-any
Tag: py3-none-any
Build: 1
#. ``Wheel-Version`` is the version number of the Wheel specification.
``Generator`` is the name and optionally the version of the software
that produced the archive. ``Root-Is-Purelib`` is true if the top
level directory of the archive should be installed into purelib;
otherwise the root should be installed into platlib. ``Tag`` is the
wheel's expanded compatibility tags; in the example the filename would
contain ``py2.py3-none-any``. ``Build`` is the build number and is
omitted if there is no build number.
#. ``Generator`` is the name and optionally the version of the software
that produced the archive.
#. ``Root-Is-Purelib`` is true if the top level directory of the archive
should be installed into purelib; otherwise the root should be installed
into platlib.
#. ``Tag`` is the wheel's expanded compatibility tags; in the example the
filename would contain ``py2.py3-none-any``.
#. ``Build`` is the build number and is omitted if there is no build number.
#. A wheel installer should warn if Wheel-Version is greater than the
version it supports, and must fail if Wheel-Version has a greater
major version than the version it supports.
@ -348,6 +347,14 @@ Why does wheel also allow S/MIME signatures?
Signed packages are only a basic building block in a secure package
update system. Wheel only provides the building block.
References
==========
.. [1] PEP acceptance
(http://mail.python.org/pipermail/python-dev/2013-February/124103.html)
Appendix
========