➜

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 ncoghlan
Recipients jcon, kristjan.jonsson, mark.dickinson, ncoghlan, paul.moore, petri.lehtinen, pitrou, pv, rupole, skrah, teoliphant, vstinner
Date 2012-01-29.01:09:51
SpamBayes Score 0.00083080586
Marked as misclassified No
Message-id <1327799394.42.0.967372448776.issue10181@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm with Antoine here - we want to be *very* conservative with what we expose through the limited API. Due to the ABI compatibility promise, anything exposed that way is very hard to change.

Keeping things out of the limited API isn't really an issue - it just means that anyone that wants to use them needs to rebuild their extensions for each new version of the C API (just as they do now).

Addings things to the stable ABI later is easy though - that's why we had Martin take all the Py_buffer related stuff out of the initial version of the limited API.
History
Date User Action Args
2012-01-29 01:09:54ncoghlansetrecipients: + ncoghlan, teoliphant, paul.moore, mark.dickinson, rupole, pitrou, kristjan.jonsson, vstinner, pv, skrah, jcon, petri.lehtinen
2012-01-29 01:09:54ncoghlansetmessageid: <1327799394.42.0.967372448776.issue10181@psf.upfronthosting.co.za>
2012-01-29 01:09:51ncoghlanlinkissue10181 messages
2012-01-29 01:09:51ncoghlancreate