Paul Ganssle <p.gans...@gmail.com> added the comment:

This is only a semi-arbitrary restriction. Realistically, `datetime` is not a 
particularly good way to represent times much older than the 17th or 18th 
century (and if you're using time zones, it gets increasingly inaccurate as you 
go further back from 1970 or the further in the future you go from the current 
time). Generally, I think the choice to keep it to positive dates is due to a 
combination of the fact that 1. it introduces a lot more edge cases (there's no 
year 0, for example) 2. it may invalidate otherwise perfectly acceptable 
assumptions that people have made in code about the sign of the component 
values and 3. it would be a rarely used feature of dubious utility. I am not 
sure that adding this feature would be worth the support burden it would bring.

There was a discussion about this on the discourse in the past, there wasn't an 
obvious consensus that it would never happen, but I would not say that there 
was much support for the idea: 
https://discuss.python.org/t/bc-date-support/582/2

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue37992>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to