➜

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 Sam Wainwright, belopolsky, p-ganssle, tim.peters
Date 2019-08-31.21:19:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567286393.81.0.704853981167.issue37992@roundup.psfhosted.org>
In-reply-to
Content 
This just isn't going to happen.  There's no agreement to be had.  For example, the proleptic Gregorian calendar _does_ have a "year 0", and so also does ISO 8601.

Version 1.0 of the XML schema spec did not have a year 0, but _claimed_ to be compatible with ISO 8601 - which it wasn't in this respect.  So version 1.1 added year 0, despite then being incompatible with version 1.0 of itself in this respect[1].

> I am not sure that adding this feature would be worth
> the support burden it would bring.

I am:  it wouldn't ;-)  

[1] https://en.wikipedia.org/wiki/Astronomical_year_numbering
History
Date User Action Args
2019-08-31 21:19:53tim.peterssetrecipients: + tim.peters, belopolsky, p-ganssle, Sam Wainwright
2019-08-31 21:19:53tim.peterssetmessageid: <1567286393.81.0.704853981167.issue37992@roundup.psfhosted.org>
2019-08-31 21:19:53tim.peterslinkissue37992 messages
2019-08-31 21:19:53tim.peterscreate