➜

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:58:32
SpamBayes Score 0.0074681444
Marked as misclassified No
Message-id <4E04FA77.1020005@v.loewis.de>
In-reply-to <1308948322.11.0.658062605041.issue11457@psf.upfronthosting.co.za>
Content 
> I didn't know that datetime is "extremely bad at representing time
> stamps", could you explain please?

- there is no easy way to convert it into "seconds since the epoch"
- any broken-down time has issues of time stamp ordering in the
  duplicate hour of switching from DST to normal time
- time zone support is flaky-to-nonexistent in the datetime module
History
Date User Action Args
2011-06-24 20:58:33loewissetrecipients: + loewis, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, nadeem.vawda, Arfrever, r.david.murray, rosslagerwall, khenriksson
2011-06-24 20:58:32loewislinkissue11457 messages
2011-06-24 20:58:32loewiscreate