[Python-Dev] accept the wheel PEPs 425, 426, 427

[Ronald Oussoren]

On 24 Oct, 2012, at 14:59, Daniel Holth <dholth at gmail.com> wrote:

> On Wed, Oct 24, 2012 at 7:04 AM, Ronald Oussoren <ronaldoussoren at mac.com> wrote:
>> 
>> On 18 Oct, 2012, at 19:29, Daniel Holth <dholth at gmail.com> wrote:
>> 
>>> I'd like to submit the Wheel PEPs 425 (filename metadata), 426
>>> (Metadata 1.3), and 427 (wheel itself) for acceptance. The format has
>>> been stable since May and we are preparing a patch to support it in
>>> pip, but we need to earn consensus before including it in the most
>>> widely used installer.
>> 
>> PEP 425:
>> 
>> * "The version is py_version_nodot. CPython gets away with no dot, but if one is needed the underscore _ is used instead"
>> 
>>   I don't particularly like replacing dots by underscores. That needed because you use the dot character in compressed tag sets, but why not use a comma to separate items in the compressed tag set?
> 
>> * "The platform tag is simply distutils.util.get_platform() with all hyphens - and periods . replaced with underscore _."
>> 
>>   Why the replacement?  The need for replacement could be avoided by using a different separator between elements of a tag (for example "~" or "+"), and furthermore the platform tag is at a know
>>   location, and hence the use of hyphens in the platform tag is harmless (use "python_tag, abi_tag, platform_tag = tag.split('-', 2)" to split the tag into its elements.
> 
> This is based on the longstanding convention of folding - and _
> (hyphen and underscore) in built distribution filenames and using - to
> separate parts.

AFAIK distutils and setuptools do not replace hyphens in the platform name in the name of bdist files.

> 
>> * "compressed tag sets"
>> 
>>   Using '"," instead of "." to separate elements of the tag set takes away the need to replace dots in tag elements, and seems more natural to me (you'd also use comma to separate the elements
>>   when you write them down in prose or python code.
> 
> I kindof like the ,
> 
> The + might transform into a space in URLs?

You're right, + is not a good choice because that character must be quoted in URLs.

Ronald