On Thu, Oct 18, 2012 at 3:23 PM, email@example.com wrote:
Zitat von Daniel Holth firstname.lastname@example.org:
On Thu, Oct 18, 2012 at 2:36 PM, email@example.com wrote:
ISTM that some important information and some elaboration is missing from PEP 425.
The PEP is currently silent on how exactly these "compatibility tags" are combined with the package name, and the file extension. This should be specified, and preferably some examples be given.
Wheel specifies how it uses the tags. You have to strip the known extension from the filename.
Hmm. The word "extension" doesn't even appear in connection with file names in the PEP (only in relation to "C extensions").
Does the PEP, or does it not, specify that a dash must be used between the package-name-and-version? Neither the words "hyphen" nor "dash" appear in the PEP, except that hyphens are used inside the tag, and that hyphens and dots in get_platform() results are replaced.
The pep was only meant to specify the tag format which is a-b-c or a.z-b-c , and some typical values of those tags. I agree that it is confusing not to include an example of a tag being used in the context of an actual file name.