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 pitrou
Recipients daniel.urban, eric.araujo, pitrou, rhettinger
Date 2011-03-20.13:35:41
SpamBayes Score 0.0009656364
Marked as misclassified No
Message-id <>
Hmm, making PyList_* an abstract API doesn't make sense to me. These functions do exactly what they say: they operate on concrete instances of list (they are documented as part of the concrete API). With that reasoning, we should have fallback paths in every function in the concrete APIs; that's a lot of complication added to these C files.

IMO we "should" (or, rather, could) instead add abstract PySequence_Append(), etc. functions if we deem it necessary (just as we already have PyMapping_Keys(), etc.).

By the way, PyList_SetItem() already has an abstract counterpart called PyObject_SetItem(), so changing this one seems useless.
Date User Action Args
2011-03-20 13:35:42pitrousetrecipients: + pitrou, rhettinger, eric.araujo, daniel.urban
2011-03-20 13:35:42pitrousetmessageid: <>
2011-03-20 13:35:42pitroulinkissue10977 messages
2011-03-20 13:35:42pitroucreate