[Python-ideas] Backward-incompatible changes for Python 4

Chris Angelico rosuav at gmail.com
Mon Apr 1 18:49:15 EDT 2019

On Tue, Apr 2, 2019 at 9:34 AM Jonathan Goble <jcgoble3 at gmail.com> wrote:
> On Mon, Apr 1, 2019 at 6:12 PM Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
>> Obviously, removing a whole day from the year will create problems
>> keeping the calendar in step with the seasons. To compensate, it
>> will be necessary to add approximately 1.25 days worth of leap
>> seconds to each year. This works out to about one leap second
>> every 5 minutes. If a suitable algorithm is devised for distributing
>> these "leap minutes" as evenly as possible over the year, this
>> should cause minimal disruption.
> Far more disruption than you think, because that would result in daylight at midnight and nighttime at noon for a good chunk of the year. Instead, I suggest permanently extending February to 29 days instead, with a 30th day in leap years. This would limit the disruption to a single month (March), and only by an offset of one day. I never understood what February did wrong to be disrespected with such a short month anyway. Instead, February would be equal in length to April most of the time, and every four years (at least within our lifetimes *cough2100cough*) it would get to gloat over being longer than April.

You don't know what heinous crimes February committed, because they
were overshadowed by March which violated the normal rules by not just
having a single id(), but multiple.

Beware the IDs of March.


More information about the Python-ideas mailing list