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 belopolsky
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, tim.peters, vstinner
Date 2010-07-02.23:38:29
SpamBayes Score 0.000688101
Marked as misclassified No
Message-id <1278113911.75.0.670250034664.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
I am attaching a patch from issue 5288 as an example of a change that I would favor more than issue7989-cmp.diff.  This patch eliminates _utcoffset and _dst methods that duplicate utcoffset and dst, but return integer minutes rather than a timedelta.

I am not checking these changes in sandbox because these are examples of how I plan to improve C implementation when datetime.py makes it into the main tree.  I envision such changes to be discussed within context of datetime.py and if approved, implemented in C and committed simultaneously.

Improving datetime.py implementation and making it diverge from C implementation defeats the purpose I see in having datetime.py in the first place.

Antoine?
History
Date User Action Args
2010-07-02 23:38:32belopolskysetrecipients: + belopolsky, lemburg, tim.peters, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-07-02 23:38:31belopolskysetmessageid: <1278113911.75.0.670250034664.issue7989@psf.upfronthosting.co.za>
2010-07-02 23:38:30belopolskylinkissue7989 messages
2010-07-02 23:38:30belopolskycreate