Message75902
| Author |
belopolsky |
| Recipients |
Neil Muller, belopolsky, davidfraser, hodgestar, tebeka, vstinner, werneck |
| Date |
2008年11月15日.01:15:26 |
| SpamBayes Score |
1.3642886e-08 |
| Marked as misclassified |
No |
| Message-id |
<1226711729.86.0.312684878446.issue2736@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I would like to voice my opposition the totimestamp method.
Representing time as a float is a really bad idea (originated at
Microsoft as I have heard). In addition to the usual numeric problems
when dealing with the floating point, the resolution of the floating
point timestamp varies from year to year making it impossible to
represent high resolution historical data.
In my opinion both time.time() returning float and
datetime.fromtimestamp() taking a float are both design mistakes and
adding totimestamp that produces a float will further promote a bad
practice.
I would not mind integer based to/from timestamp methods taking and
producing seconds or even (second, microsecond) tuples, but I don't
think changing fromtimestamp behavior is an option. |
|