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, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, vstinner
Date 2010-06-24.22:04:55
SpamBayes Score 0.00472095
Marked as misclassified No
Message-id <>
Why do you need a pure Python version of datetime:
 - it's easier to work on a new feature first in Python: there are more people are able to write Python code, than people able to write C code (especially C code using the Python C API)
 - it helps datetime debuging
 - it helps other Python implementations (not only PyPy)
 - it improves the quality of the tests and so of the C version

I think that the first point is the most important, but datetime still lack many feature and is far from being perfect.

I don't think that the pure Python implementation should be used by default: the current C implementation should stay because it's faster and many people use it. I don't know the best name for the Python version, maybe (or



 - @Alexander: did you contacted people from IronPython and Jython?
 - Is the Python version compatible with the C version about the serialization (pickle)?


r.david.murray> there may be more important stuff to python

You cannot force other developer to work on a specific topic since Python is only developed by hackers in their free time. If Alexander would like to work on this, he have to do it :-)
Date User Action Args
2010-06-24 22:04:58vstinnersetrecipients: + vstinner, lemburg, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, belopolsky, pitrou, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-24 22:04:57vstinnersetmessageid: <>
2010-06-24 22:04:55vstinnerlinkissue7989 messages
2010-06-24 22:04:55vstinnercreate