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 Paul Pinterits
Recipients Paul Pinterits, martin.panter
Date 2017-04-02.22:53:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491173585.78.0.833911831101.issue29964@psf.upfronthosting.co.za>
In-reply-to
Content
No no, the docs are correct. This was definitely my mistake. I'm just trying to say that it's rather confusing how there's only partial support for time zones. When I saw that there is support for parsing the time zone offset, I assumed that the functions provided in the time module would be enough to solve my problem - having to rely on the datetime module to have proper time zone support caught me by surprise. It's quite counterintuitive.
History
Date User Action Args
2017-04-02 22:53:05Paul Pinteritssetrecipients: + Paul Pinterits, martin.panter
2017-04-02 22:53:05Paul Pinteritssetmessageid: <1491173585.78.0.833911831101.issue29964@psf.upfronthosting.co.za>
2017-04-02 22:53:05Paul Pinteritslinkissue29964 messages
2017-04-02 22:53:05Paul Pinteritscreate