➜

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 belopolsky
Recipients ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, pitrou, rafe, vstinner
Date 2010-05-25.23:44:30
SpamBayes Score 0.019261694
Marked as misclassified No
Message-id <1274831072.99.0.797476666772.issue5094@psf.upfronthosting.co.za>
In-reply-to
Content 
Brett: "[utcnow] should at least get deprecated with a message saying that people should be using ``now(utc)``"

Yes, I believe all utcxxx methods of datetime are a kludge due to the lack of concrete UTC tzinfo:

utcfromtimestamp() -> fromtimestamp(utc)
t.utctimetuple() -> t.replace(tzinfo=utc).timetuple()
History
Date User Action Args
2010-05-25 23:44:33belopolskysetrecipients: + belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-05-25 23:44:32belopolskysetmessageid: <1274831072.99.0.797476666772.issue5094@psf.upfronthosting.co.za>
2010-05-25 23:44:30belopolskylinkissue5094 messages
2010-05-25 23:44:30belopolskycreate