Message110535
| 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 |
<1279331373.7.0.543169967836.issue9079@psf.upfronthosting.co.za> |
| 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 |
|