Author vstinner
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, davidfraser, eric.araujo, giampaolo.rodola, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, tim.peters, vstinner
Date 2010-08-13.02:26:01
SpamBayes Score 2.06422e-11
Marked as misclassified No
Message-id <1281666364.27.0.384776817221.issue9528@psf.upfronthosting.co.za>
In-reply-to
Content
> 1. Datetime.py time source (time.time()) represents time as 
> a floating point number which leads to system dependent behavior
> and introduces floating point operations where they are not needed.

Why not introducing a new function in time module? Other people may benefit from this.

> 3. The datetime module could benefit from access to tm_zone 
> and tm_gmtoff components of the tm structure, but introducing 
> those in the output of time.localtime() would require either 
> hidden member hackery or loss of backwards compatibility.
> See issues #1647654, #7662, and #9527.

Why not creating a new function giving access to all tm attributes? Eg. time.localtime_gmaware()?

> 4. No changes will be done to timemodule.c other than renaming

What about time_strftime()? It is 170 lines long: will it be moved to _basictime.c? You have to keep the code filling the "struct tm" structure in (_)timemodule.c.
History
Date User Action Args
2010-08-13 02:26:04vstinnersetrecipients: + vstinner, lemburg, tim.peters, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, davidfraser, belopolsky, pitrou, techtonik, giampaolo.rodola, eric.araujo, r.david.murray, brian.curtin, daniel.urban
2010-08-13 02:26:04vstinnersetmessageid: <1281666364.27.0.384776817221.issue9528@psf.upfronthosting.co.za>
2010-08-13 02:26:02vstinnerlinkissue9528 messages
2010-08-13 02:26:01vstinnercreate