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, doko, dstufft, eric.snow, lemburg, ncoghlan, ned.deily, pitrou, python-dev, steve.dower, tim.golden, zach.ware
Date 2015-04-16.22:34:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <55303907.2030909@egenix.com>
In-reply-to <1429208484.21.0.0944838473594.issue22980@psf.upfronthosting.co.za>
Content
On 16.04.2015 20:21, Ned Deily wrote:
> 
> Ned Deily added the comment:
> 
>> No, PEP 3149 is about the Python ABI, following PEP 3147,
>> which implements this for PYC files.
> 
>> The intent is to be able to have mutliple *Python* ABI/API versions
>> installed side-by-side, not multiple platform ABI versions :-)
> 
> Well, for all practical purposes, the platform *is* part of the ABI :=)

Yes, but if all your files on your box share the same ABI, do you
really want to have all of them come with an extra name extension ?
I mean: If all your apples are green, would you write "green" on them to
remember ? ;-)

All Linux distributions I know place the 32-bit and 64-bit versions
of shared libs into different directories rather than putting them all
into a single dir and adding ABI flags to the .so files.
Windows does this too. FreeBSD as well.

Why should Python behave differently ? Just because we can is not
really a good answer, IMO.
History
Date User Action Args
2015-04-16 22:34:55lemburgsetrecipients: + lemburg, barry, doko, ncoghlan, pitrou, tim.golden, ned.deily, Arfrever, python-dev, eric.snow, zach.ware, steve.dower, dstufft
2015-04-16 22:34:55lemburglinkissue22980 messages
2015-04-16 22:34:55lemburgcreate