◐ Shell
reader mode source ↗

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 Daniel.O'Connor, belopolsky, bignose, brett.cannon, r.david.murray
Date 2011-08-16.18:16:48
SpamBayes Score 0.0007153525
Marked as misclassified No
Message-id <1313518609.06.0.322121064803.issue12756@psf.upfronthosting.co.za>
In-reply-to
Content
This is for backwards-compatibility as the UTC object did not come into existence until (I believe) Python 2.7. The docs for utcnow() explicitly state that if you want a timezone-aware UTC datetime object that you should use now() w/ the UTC object passed in.

Now if you would like to have a keyword argument for utcnow() to cause it to return a UTC object (e.g., utcnow(aware=True)), that may be a patch that  could get accepted as it doesn't break backwards-compatibility if you leave the argument out.
History
Date User Action Args
2011-08-16 18:16:49brett.cannonsetrecipients: + brett.cannon, belopolsky, r.david.murray, bignose, Daniel.O'Connor
2011-08-16 18:16:49brett.cannonsetmessageid: <1313518609.06.0.322121064803.issue12756@psf.upfronthosting.co.za>
2011-08-16 18:16:48brett.cannonlinkissue12756 messages
2011-08-16 18:16:48brett.cannoncreate