News for hackers. Stuff that matters.
Re:Mercurial’s journey to and reflections on Python 3 by mixmastamyk on Monday January 13, 2020 @04:10PM (#22038622)
Yes, I was really surprised that they avoided upgrading to Python 2.7-level best practices and future statements for as long as they did and tried to hide it from most developers thru custom compatibility layers. Huh? That's step 0, getting except, stdlib imports, and print statements up to date. Folks can deal with that, that's the easy part.

Keeping blame details (and line-lengths, ha!) was given as the excuse and that is a nice feature and all. However they could have copied the repo over before porting to keep that information and saved time. Wouldn't be surprised if it was eventually lost anyway.

Re:Mercurial’s journey to and reflections on Python 3 by indygreg2 on Monday January 13, 2020 @09:55PM (#22041374)
The late start was mostly due to having to retain Python 2.4/2.5 compatibility until May 2015 and it was literally impossible to use some future statements or some Python 3 syntax until 2.6 was required. I have updated the post to reflect this.
Re:Mercurial’s journey to and reflections on Python 3 by mixmastamyk on Monday January 13, 2020 @10:33PM (#22041582)
IC, that’s unfortunate. Believe that is the time to cut a legacy branch/release rather than block progress for a decade.