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.
Created on 2017-01-22 17:47 by Eli Collins, last changed 2022-04-11 14:58 by admin. This issue is now closed.
Files | ||||
---|---|---|---|---|
File name | Uploaded | Description | Edit | |
dump_timestamp_output.py | Eli Collins, 2017-01-22 17:47 |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:58:42 | admin | set | github: 73532 |
2017-01-27 14:58:10 | vstinner | set | status: open -> closed superseder: datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6 messages: + msg286360 |
2017-01-27 14:57:37 | vstinner | set | title: datetime.utcfromtimestamp() returns strange result for very large values -> datetime doesn't check for min/max dates anymore in Python 3.6.0 => crash |
2017-01-23 15:16:59 | Eli Collins | set | resolution: duplicate messages: + msg286091 |
2017-01-22 23:45:01 | belopolsky | set | keywords:
+ 3.6regression nosy: + vstinner messages: + msg286034 |
2017-01-22 18:52:42 | lemburg | set | messages: + msg286025 |
2017-01-22 18:24:57 | serhiy.storchaka | set | nosy:
+ lemburg, belopolsky |
2017-01-22 17:47:34 | Eli Collins | create |