Author belopolsky
Recipients belopolsky, lemburg, ncoghlan, pitrou
Date 2012-02-22.03:25:14
SpamBayes Score 0.00286588
Marked as misclassified No
Message-id <1329881119.11.0.292426322817.issue14083@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-02-22 03:25:19belopolskysetrecipients: + belopolsky, lemburg, ncoghlan, pitrou
2012-02-22 03:25:19belopolskysetmessageid: <1329881119.11.0.292426322817.issue14083@psf.upfronthosting.co.za>
2012-02-22 03:25:15belopolskylinkissue14083 messages
2012-02-22 03:25:14belopolskycreate