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 r.david.murray
Recipients belopolsky, docs@python, leewz, lemburg, r.david.murray
Date 2015-10-17.02:15:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445048112.15.0.137937767622.issue25428@psf.upfronthosting.co.za>
In-reply-to
Content
timezone is relatively new.  Work is in progress to add better timezone support to datetime, but it is a complicated subject and may or may not make it into 3.6.  In any case I think it is too soon to talk about this kind of API change, before the other work gets farther along.  That's probably also true for changes to the docs, although a concrete proposal there might have some chance.

There's a mailing list for talking specifically about datetime issues, you might want to post there (see mail.python.org, datetime-sig).
History
Date User Action Args
2015-10-17 02:15:12r.david.murraysetrecipients: + r.david.murray, lemburg, belopolsky, docs@python, leewz
2015-10-17 02:15:12r.david.murraysetmessageid: <1445048112.15.0.137937767622.issue25428@psf.upfronthosting.co.za>
2015-10-17 02:15:12r.david.murraylinkissue25428 messages
2015-10-17 02:15:11r.david.murraycreate