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 tim.peters
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, tim.peters, vstinner
Date 2010-06-25.23:11:19
SpamBayes Score 0.0148913
Marked as misclassified No
Message-id <1277507490.09.0.413520823138.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
> It would be great if you could shed
> some light on the history behind pure
> python implementation.  Why was it
> developed in the first place?

It was rapid prototyping - design decisions were changing daily, and it goes a lot faster to change Python code than C code.

> What was the reason not to ship it
> with python?

Didn't want to create new ongoing maintenance burdens.  Multiple implementations eventually drift out of synch, and at the time we had had enough of that already wrt, e.g., pickle vs cPickle.

Sorry, nothing deep here ;-)
History
Date User Action Args
2010-06-25 23:11:30tim.peterssetrecipients: + tim.peters, lemburg, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, belopolsky, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-25 23:11:30tim.peterssetmessageid: <1277507490.09.0.413520823138.issue7989@psf.upfronthosting.co.za>
2010-06-25 23:11:20tim.peterslinkissue7989 messages
2010-06-25 23:11:19tim.peterscreate