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 xiang.zhang
Recipients belopolsky, bozo.kopic, ghaering, lemburg, serhiy.storchaka, xiang.zhang
Date 2017-01-13.09:19:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I think the old code unlikely will be broken if preserve an exception type and don't change conditions for raising an error.

Currently there could be no error when the object gets a timezone. The timezone is simply discarded and only when microseconds comes to 0 there is a ValueError. I don't think the user code would prepare to catch the ValueError. I don't oppose make timestamp more strict but just not sure if it's suitable.
Date User Action Args
2017-01-13 09:19:45xiang.zhangsetrecipients: + xiang.zhang, lemburg, ghaering, belopolsky, serhiy.storchaka, bozo.kopic
2017-01-13 09:19:45xiang.zhangsetmessageid: <>
2017-01-13 09:19:45xiang.zhanglinkissue29099 messages
2017-01-13 09:19:44xiang.zhangcreate