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 Trundle, daniel.urban, eric.araujo, ncoghlan, pitrou, rhettinger
Date 2011-03-20.21:50:55
SpamBayes Score 5.0938707e-09
Marked as misclassified No
Message-id <>
It's largely a backwards compatibility hack, but the concrete methods also have an optimised fast path that the generic methods lack.

So (for example), PyList_SetItem would now mean "this is *probably* a list, so check for that and use the fast path if the assumption is correct, otherwise fall back on PyObject_SetItem".

Currently, using the concrete API means your code potentially *breaks* if the assumption is incorrect.

Sounds like a good idea to me, and will fix a lot of cases of bad interaction between concrete types and related objects.
Date User Action Args
2011-03-20 21:50:56ncoghlansetrecipients: + ncoghlan, rhettinger, pitrou, eric.araujo, Trundle, daniel.urban
2011-03-20 21:50:56ncoghlansetmessageid: <>
2011-03-20 21:50:56ncoghlanlinkissue10977 messages
2011-03-20 21:50:55ncoghlancreate