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 belopolsky, brian.curtin, lemburg, r.david.murray
Date 2010-06-07.08:06:14
SpamBayes Score 0.00204074
Marked as misclassified No
Message-id <4C0CA874.8090204@egenix.com>
In-reply-to <1275788127.21.0.430829926194.issue7989@psf.upfronthosting.co.za>
Content
Alexander Belopolsky wrote:
> 
> Alexander Belopolsky <belopolsky@users.sourceforge.net> added the comment:
> 
> As far as I remember, the datetime module started as a pure python module and was reimplemented in C around year 2003 or so.  One of the important additions at that time was the C API to datetime functionality.  I am afraid that with the _timemodule.c/timemodule.py split there will be more an more functionality that is awkward to access from C API.

That's correct, though the main reason for rewriting the module in
C was to gain performance - this is essential for basic types like
date/time types.

-1 on undoing the C rewrite.

It would be much better to spell out the problems you mention and
provide patches to implement solutions for them.
History
Date User Action Args
2010-06-07 08:06:17lemburgsetrecipients: + lemburg, belopolsky, r.david.murray, brian.curtin
2010-06-07 08:06:15lemburglinkissue7989 messages
2010-06-07 08:06:14lemburgcreate