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 r.david.murray
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, vstinner
Date 2010-06-18.18:49:19
SpamBayes Score 0.011107028
Marked as misclassified No
Message-id <1276886962.06.0.654868320051.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
My understanding is that the desire to have pure python versions of standard library modules is to decouple the standard library from dependency on CPython as far as practical.  Perhaps all existing Python implementations have dealt with datetime somehow, but what about new implementations?  Having a pure Python version would help developers of new implementations get started, even if they later decided to reimplement it more natively (as CPython has done).
History
Date User Action Args
2010-06-18 18:49:22r.david.murraysetrecipients: + r.david.murray, lemburg, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, belopolsky, pitrou, vstinner, techtonik, brian.curtin, daniel.urban
2010-06-18 18:49:22r.david.murraysetmessageid: <1276886962.06.0.654868320051.issue7989@psf.upfronthosting.co.za>
2010-06-18 18:49:20r.david.murraylinkissue7989 messages
2010-06-18 18:49:20r.david.murraycreate