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 vstinner
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, r.david.murray, techtonik, vstinner
Date 2010-06-10.10:48:49
SpamBayes Score 0.0008385415
Marked as misclassified No
Message-id <1276166931.63.0.284106214297.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
I like the idea of a pure Python implementation of the datetime module, for different reasons:
 - it will become the reference implementation
 - other Python interpreters can use it
 - it can be used to test another implementation, eg. the current C version
 - implement/test a new feature is much faster in Python than in C

About the last point: I already used _pyio many times to fix a bug or to develop a new feature. _pyio helps to choice the right solution because you can easily write a short patch and so compare different solutions.

If other Python interpreters have already their Python implementation, we can just choose the best one, and patch it to add last new features of the C version.
History
Date User Action Args
2010-06-10 10:48:51vstinnersetrecipients: + vstinner, lemburg, brett.cannon, amaury.forgeotdarc, belopolsky, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-10 10:48:51vstinnersetmessageid: <1276166931.63.0.284106214297.issue7989@psf.upfronthosting.co.za>
2010-06-10 10:48:50vstinnerlinkissue7989 messages
2010-06-10 10:48:49vstinnercreate