[Python-3000] Modules with Dual Python/C Implementations (original) (raw)
Brett Cannon brett at python.org
Mon Dec 11 21:10:34 CET 2006
- Previous message: [Python-3000] Modules with Dual Python/C Implementations
- Next message: [Python-3000] Modules with Dual Python/C Implementations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/10/06, Calvin Spealman <ironfroggy at gmail.com> wrote:
Has anyone considered consolidating the module pairs that have both a C and Python implementation? For example, pickle and cPickle and StingIO and cStringIO. It seems like keeping both around might be counter productive. It leads to more code for bugs, issues when there are accidental differences between the two, leading to misdiagnosed errors or hard to find bugs when people test with pickle and run with cPickle. Just seems like all around, if there was found to be a reason to make a module in C over its original Python version, the original doesn't need to stick around.
This has been argued about before. It has been suggested we actually ditch the C version since we only want to maintain one version and the Python version can be used by alternative Python implementations.
This probably needs to be covered in a PEP that covers a stdlib reorg/renaming.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-3000/attachments/20061211/2cbac386/attachment.html
- Previous message: [Python-3000] Modules with Dual Python/C Implementations
- Next message: [Python-3000] Modules with Dual Python/C Implementations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]