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 brett.cannon
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, r.david.murray, techtonik
Date 2010-06-08.18:09:36
SpamBayes Score 0.0116135
Marked as misclassified No
Message-id <1276020578.25.0.642954542569.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
So yes, cPickle/pickle, cStringIO/StringIO, heapq, etc. are all examples of the approach. One could choose to write the pure Python version first, profile the code, and only write extension code for the hot spots, but obviously that typically doesn't happen.

As for who maintains it, that's python-dev, just like every other module that is structured like this. When the stdlib gets more of a clear separation from CPython I suspect the other VM maintainers will contribute more.

As for PyPy not specifically needing this, that still doesn't solve the problem that Jython and IronPython have with extension code or any other future VM that doesn't try to come up with a solution for extensions.
History
Date User Action Args
2010-06-08 18:09:38brett.cannonsetrecipients: + brett.cannon, lemburg, amaury.forgeotdarc, belopolsky, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-08 18:09:38brett.cannonsetmessageid: <1276020578.25.0.642954542569.issue7989@psf.upfronthosting.co.za>
2010-06-08 18:09:36brett.cannonlinkissue7989 messages
2010-06-08 18:09:36brett.cannoncreate