These all introduce or update existing Python Packaging Specifications,
and should follow the PyPA Specification processes. These are expected
to be Standards Track PEPs and are not informational.
This change also ensures that they get listed under the correct section
on the Packaging topic index.
Per GH-560, the current definition of `python_version` is not compatible
with a 2+ digit major or minor version. There were no objections to
changing the definition to more accurately reflect the semantic content
intended to be conveyed (i.e. the major and minor version).
* Change the specification example to be clearer.
Previously, we compared python_version < "2.7.10".
As python_version only keeps the major and minor number (2.7, 3.2),
it could lead to unexpected behaviour when comparing to 3-parts versions.
Changing the example might reduce the risk of making that small but
confusing mistake.
* Fix mistake in Backwards Compatibility about python_version.
In this section, it said:
"handle version comparisons with python_version "2.7.10" differently."
while is should have mentionned python_full_version, as python_version
will never have a 3-part version value.
Pradyun Gedam
Adam Turner
Yuki Nihei
Christopher Hunt
Paul Ganssle
Min ho Kim
Kevin
Michael Laing
Mariatta
Huang Huang
Brett Cannon
Vincent Philippon
Nick Coghlan
Marti Raudsepp
Donald Stufft