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 tim.peters
Recipients Han Shaowen, ned.deily, tim.peters
Date 2018-04-18.03:11:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
docstrings give brief statements intended to jog your memory; they're not intended to be comprehensive docs.  Read the actual documentation and see whether you're still confused.  When you "assumed it is irrelevant to time zone", that was your _assumption_, which the actual docs would have clarified.

The whole story simply can't be told here without docs that make the distinction between "naive" and "aware" datetime objects, and the connection to what your platform's C mktime() function does about your local time zone.  The brief docstring is correct that a POSIX timestamp is returned (a count of seconds from the UTC epoch).  But how that relates to the datetime object requires reading the docs, not blind guessing ;-)
Date User Action Args
2018-04-18 03:11:33tim.peterssetrecipients: + tim.peters, ned.deily, Han Shaowen
2018-04-18 03:11:33tim.peterssetmessageid: <>
2018-04-18 03:11:33tim.peterslinkissue33293 messages
2018-04-18 03:11:33tim.peterscreate