This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients Arfrever, barry, brett.cannon, eric.snow, lemburg, ncoghlan, ned.deily, pitrou, steve.dower, tim.golden, vstinner, zach.ware
Date 2014-12-02.19:51:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <547E1834.40607@egenix.com>
In-reply-to <547E0EA8.6000704@free.fr>
Content
On 02.12.2014 20:10, Antoine Pitrou wrote:
> 
> Antoine Pitrou added the comment:
> 
> Le 02/12/2014 19:59, Marc-Andre Lemburg a écrit :
>>
>> My main point was that we shouldn't start adding tags for e.g.
>> PPC, Intel, ARM, etc. since platforms needing to support multiple
>> such architectures will typically support fat builds anyway.
>>
>> How about using these flags:
>>
>> b0 - 16-bit
>> b1 - 32-bit
>> b2 - 64-bit
>> b3 - 128-bit
> 
> Fair enough, although I think we only need 32-bit and 64-bit for now,
> and "32b" vs. "64b" would probably be more readable :-)

True, I'm just not sure what the parsing requirements are and
the ABI version names are too long already, IMO. PEP 425 used
a nice short variant for the Python part.
History
Date User Action Args
2014-12-02 19:51:22lemburgsetrecipients: + lemburg, barry, brett.cannon, ncoghlan, pitrou, vstinner, tim.golden, ned.deily, Arfrever, eric.snow, zach.ware, steve.dower
2014-12-02 19:51:22lemburglinkissue22980 messages
2014-12-02 19:51:21lemburgcreate