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 lemburg
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, r.david.murray, techtonik, vstinner
Date 2010-06-10.11:03:02
SpamBayes Score 4.1258245e-06
Marked as misclassified No
Message-id <4C10C665.6050005@egenix.com>
In-reply-to <1276166931.63.0.284106214297.issue7989@psf.upfronthosting.co.za>
Content
STINNER Victor wrote:
> 
> STINNER Victor <victor.stinner@haypocalc.com> added the comment:
> 
> 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.

Ah, so that where the Python io module hides. Thanks for the pointer.
History
Date User Action Args
2010-06-10 11:03:04lemburgsetrecipients: + lemburg, brett.cannon, amaury.forgeotdarc, belopolsky, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-10 11:03:02lemburglinkissue7989 messages
2010-06-10 11:03:02lemburgcreate