➜

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 loewis
Recipients Arfrever, belopolsky, jcea, khenriksson, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall, vstinner
Date 2011-06-24.20:36:28
SpamBayes Score 3.7725194e-06
Marked as misclassified No
Message-id <4E04F54B.8050206@v.loewis.de>
In-reply-to <1308945338.07.0.729077321016.issue11457@psf.upfronthosting.co.za>
Content 
> Hey, why nobody proposed datetime.datetime objects?

datetime.datetime is extremely bad at representing time stamps.
Don't use broken-down time if you can avoid it.

> By the way, Windows does also use timestamps with a nanosecond
> resolution, it's not specific to POSIX!

Actually, it doesn't. The Windows filetime data type uses units
of 100ns, starting on 1.1.1601.
History
Date User Action Args
2011-06-24 20:36:29loewissetrecipients: + loewis, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, nadeem.vawda, Arfrever, r.david.murray, rosslagerwall, khenriksson
2011-06-24 20:36:28loewislinkissue11457 messages
2011-06-24 20:36:28loewiscreate