[issue31212] datetime: min date (0001-01-01 00:00:00) can't be converted to local timestamp
Alexander Belopolsky
report at bugs.python.org
Wed Aug 16 17:57:10 EDT 2017
Alexander Belopolsky added the comment:
On the second thought, a reasonable design can use datetime.min/max as placeholders for unknown times far in the past/future compensating for the lack datetime ±inf. In this use case, it may be annoying to see errors from timestamp() instead of some ridiculously large values.
I am -0 on making this change. If anyone is motivated to produce a patch - I'll review it, but I am not going to write it myself.
I am marking this "tests needed" because we need a test complete with setting an appropriate timezone that demonstrates this issue.
----------
components: +Extension Modules
stage: -> test needed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue31212>
_______________________________________
More information about the Python-bugs-list
mailing list