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 loewis
Recipients belopolsky, casevh, georg.brandl, jimjjewett, ked-tao, loewis, mark.dickinson, pitrou, rhettinger, tim.peters
Date 2010-09-05.16:59:06
SpamBayes Score 1.4016815e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
Am 05.09.2010 13:12, schrieb Antoine Pitrou:
> Antoine Pitrou <> added the comment:
>> Correct. So it either needs to happen before 3.2, or wait until 4.0,
> Shouldn't there be a provision for ABI versioning?

There is certainly support for ABI versioning; the ABI version defined
in the PEP is called "python3.dll".

> Or do you suggest bumping to the next major 
> number (4.0, 5.0...) be done on the basis of ABI changes?

No, vice versa. The PEP promises that the ABI won't change until Python
4. For any change that might break the ABI, either a
backwards-compatible solution needs to be found, or the change be
deferred to Python 4.
Date User Action Args
2010-09-05 16:59:09loewissetrecipients: + loewis, tim.peters, georg.brandl, rhettinger, jimjjewett, mark.dickinson, belopolsky, pitrou, casevh, ked-tao
2010-09-05 16:59:07loewislinkissue9778 messages
2010-09-05 16:59:06loewiscreate