Author belopolsky
Recipients ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, pitrou, rafe, vstinner
Date 2010-05-25.22:14:33
SpamBayes Score 0.0131785
Marked as misclassified No
Message-id <1274825674.46.0.797822552753.issue5094@psf.upfronthosting.co.za>
In-reply-to
Content
Note that Brett has already mentioned backward compatibility issues, but suggested that "[adding tz_aware argument may provide] a transition plan to make utcnow() always return a timezone-aware datetime object." [msg106413]

I would say, lets leave utcnow() alone.  It is ugly enough without a boolean argument.  I don't see how datetime.now(utc) can be too error prone.  I think Brett's comment about a stupid developer was about passing tzinfo instead of bool to utcnow() and that I agree makes no sense.
History
Date User Action Args
2010-05-25 22:14:34belopolskysetrecipients: + belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-05-25 22:14:34belopolskysetmessageid: <1274825674.46.0.797822552753.issue5094@psf.upfronthosting.co.za>
2010-05-25 22:14:33belopolskylinkissue5094 messages
2010-05-25 22:14:33belopolskycreate