[issue37992] Change datetime.MINYEAR to allow for negative years

Change by Terry J. Reedy : -- resolution: -> rejected stage: -> resolved status: open -> closed versions: +Python 3.9 -Python 3.7 ___ Python tracker ___

[issue37992] Change datetime.MINYEAR to allow for negative years

Tim Peters added the comment: 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

[issue37992] Change datetime.MINYEAR to allow for negative years

Paul Ganssle 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

[issue37992] Change datetime.MINYEAR to allow for negative years

Change by Karthikeyan Singaravelan : -- nosy: +belopolsky, p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37992] Change datetime.MINYEAR to allow for negative years

New submission from Sam Wainwright : The value of datetime.MINYEAR (1) seems arbitrarily restrictive. There are plenty of reasons why users of the standard library might want to work with negative years. Workarounds involving things like astropy don't work in all cases, particularly when

[issue37992] Change datetime.MINYEAR to allow for negative years

Change by Sam Wainwright : -- components: Library (Lib) nosy: Sam Wainwright priority: normal severity: normal status: open title: Change datetime.MINYEAR to allow for negative years type: enhancement versions: Python 3.7 ___ Python tracker