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 rhettinger
Recipients amaury.forgeotdarc, benjamin.peterson, christian.heimes, exarkun, giampaolo.rodola, ialbert, pitrou, rhettinger, wplappert
Date 2009-02-19.22:32:18
SpamBayes Score 1.0654286e-05
Marked as misclassified No
Message-id <1235082741.86.0.771497180013.issue4565@psf.upfronthosting.co.za>
In-reply-to
Content
[Benjamin Peterson]
> I think we should just drop the Python implementations. There's no point
> in trying to keep two implementations around.

I disagree.  I've found great value in keeping a pure python version
around for things I've converted to C.   The former serves as
documentation, as a tool for other implementations (like PyPy
IronPython, and Jython), and as a precise spec.  The latter case
is especially valuable (otherwise, the spec becomes whatever
CPython happens to do). 

Also, I've found that once the two are in-sync, keeping it that way
isn't hard.  And, there effort for keeping them in-sync is a good
way to find bugs.

In the heapqmodule, we do a little magic in the test suite to
make sure the tests are run against both.  It's not hard.


Raymond
History
Date User Action Args
2009-02-19 22:32:21rhettingersetrecipients: + rhettinger, exarkun, amaury.forgeotdarc, pitrou, giampaolo.rodola, christian.heimes, benjamin.peterson, wplappert, ialbert
2009-02-19 22:32:21rhettingersetmessageid: <1235082741.86.0.771497180013.issue4565@psf.upfronthosting.co.za>
2009-02-19 22:32:19rhettingerlinkissue4565 messages
2009-02-19 22:32:18rhettingercreate