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 mirkovogt
Recipients belopolsky, mirkovogt, r.david.murray
Date 2015-01-27.19:20:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422386427.73.0.0681076077935.issue23332@psf.upfronthosting.co.za>
In-reply-to
Content
I got that - so marking utcnow() as deprecated seems like a good idea.
But it's not just about utcnow() but also now().

now() also doesn't return any timezone stated by default - which I would still consider as a bug. However making now() require a TZ being specified would probably also break a lot of code. But then, using function called isoformat() - on whatever object, naive or not - I'd expect a timezone being specified - since that's what I finally think the ISO-standard actually says.

I see that my initial proposal doesn't work out, but I'm still not happy with the current situation I'm however also not sure how to change properly without breaking existing code using those functions.
History
Date User Action Args
2015-01-27 19:20:27mirkovogtsetrecipients: + mirkovogt, belopolsky, r.david.murray
2015-01-27 19:20:27mirkovogtsetmessageid: <1422386427.73.0.0681076077935.issue23332@psf.upfronthosting.co.za>
2015-01-27 19:20:27mirkovogtlinkissue23332 messages
2015-01-27 19:20:27mirkovogtcreate