➜

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 SilentGhost
Recipients Piotr Kamoda, SilentGhost
Date 2019-05-13.09:32:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557739970.71.0.893342796812.issue36899@roundup.psfhosted.org>
In-reply-to
Content 
The utcfromtimestamp returns a naïve object that is assumed to be in the UTC timezone, you're then effectively turning it into a aware object in CEST timezone. I'm not sure what you think is wrong with utcfromtimestamp here, but it behaves according to documentation.
History
Date User Action Args
2019-05-13 09:32:50SilentGhostsetrecipients: + SilentGhost, Piotr Kamoda
2019-05-13 09:32:50SilentGhostsetmessageid: <1557739970.71.0.893342796812.issue36899@roundup.psfhosted.org>
2019-05-13 09:32:50SilentGhostlinkissue36899 messages
2019-05-13 09:32:50SilentGhostcreate