Message 110535 - Python tracker

➜

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	belopolsky, georg.brandl, mark.dickinson, pitrou, rhettinger, rnk, tim.golden, tim.peters
Date	2010-07-17.01:49:28
SpamBayes Score	0.007493831
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
It turns out I misunderstood how date.today() worked [1] and issue9079.diff introduced significant change in behavior. Bringing timeofday into core rather than _time.c also introduced several complications. As a result it makes sense to start with just internal restructuring: bring gettimeofday into core and reuse it in time.time and datetime.datetime.now. The new patch, issue9079a.diff contains no user visible changes. [1] "Curious datetime method" http://mail.python.org/pipermail/python-dev/2010-July/102003.html

It turns out I misunderstood how date.today() worked [1] and issue9079.diff introduced significant change in behavior.  Bringing timeofday into core rather than _time.c also introduced several complications.  As a result it makes sense to start with just internal restructuring: bring gettimeofday into core and reuse it in time.time and datetime.datetime.now.  The new patch, issue9079a.diff contains no user visible changes.


[1] "Curious datetime method" http://mail.python.org/pipermail/python-dev/2010-July/102003.html

History
Date	User	Action	Args
2010-07-17 01:49:34	belopolsky	set	recipients: + belopolsky, tim.peters, georg.brandl, rhettinger, mark.dickinson, pitrou, tim.golden, rnk
2010-07-17 01:49:33	belopolsky	set	messageid: <[email protected]>
2010-07-17 01:49:31	belopolsky	link	issue9079 messages
2010-07-17 01:49:31	belopolsky	create