Marc-Andre Lemburg <m...@egenix.com> added the comment:
Hi Tony, from practical experience, it is a whole lot better to not deal with timezones in data processing code at all, but instead only use naive UTC datetime values everywhere, expect when you have to prepare reports or output which has a requirement to show datetime value in local time or some specific timezone. You convert all datetime values into UTC upon input, possibly store the timezone somewhere, if that is relevant for later reporting, and then forget about timezones. Your code will run faster, become a lot easier to understand and you avoid many pitfalls that TZs have, esp. when TZs are silently dropped interfacing to e.g. numeric code, databases or other external code. There's a reason why cloud code (and a lot of other code, such as data science code) has standardized on UTC :-) Cheers, -- Marc-Andre Lemburg eGenix.com ---------- nosy: +lemburg _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue12756> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
