<br><br><div><span class="gmail_quote">On 12/10/06, <b class="gmail_sendername">Calvin Spealman</b> <<a href="mailto:ironfroggy@gmail.com">ironfroggy@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Has anyone considered consolidating the module pairs that have both a<br>C and Python implementation? For example, pickle and cPickle and<br>StingIO and cStringIO. It seems like keeping both around might be<br>counter productive. It leads to more code for bugs, issues when there
<br>are accidental differences between the two, leading to misdiagnosed<br>errors or hard to find bugs when people test with pickle and run with<br>cPickle. Just seems like all around, if there was found to be a reason<br>
to make a module in C over its original Python version, the original<br>doesn't need to stick around.</blockquote><div><br>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.
<br><br>This probably needs to be covered in a PEP that covers a stdlib reorg/renaming.<br><br>-Brett<br></div><br></div><br>