Alexander Belopolsky <alexander.belopol...@gmail.com> added the comment:
The problem with this idea is that while evaluating datetime.datetime.now(datetime.timezone()), python will have to query the real time clock twice (first in timezone() and then in now()). At a particularly unfortunate time this may result in an error. Unlikely? Yes, but I would not board a python powered airplane if this problem was in the standard library. I gave a lot of thought to the problem of supporting timezone aware local time and issue9527 was the best solution I was able to come up with. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14083> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
