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 brett.cannon
Recipients brett.cannon
Date 2009-01-29.00:52:41
SpamBayes Score 1.9085121e-07
Marked as misclassified No
Message-id <1233190363.25.0.24659427347.issue5094@psf.upfronthosting.co.za>
In-reply-to
Content
When you call datetime.datetime.utcnow() you get back a naive datetime
object. But why? You asked for UTC as the timezone based on what method
call you made. And UTC is a very concrete timezone that never changes.

It would be nice to have a concrete UTC tzinfo class that utcnow() uses
so that at least those datetime instances are non-naive.

If people have no issues with making this happen I will write the code
for the concrete UTC tzinfo instance and make the appropriate changes to
utcnow().
History
Date User Action Args
2009-01-29 00:52:43brett.cannonsetrecipients: + brett.cannon
2009-01-29 00:52:43brett.cannonsetmessageid: <1233190363.25.0.24659427347.issue5094@psf.upfronthosting.co.za>
2009-01-29 00:52:42brett.cannonlinkissue5094 messages
2009-01-29 00:52:41brett.cannoncreate