News for hackers. Stuff that matters.
Re:Mercurial’s journey to and reflections on Python 3 by falcolas on Monday January 13, 2020 @02:39PM (#22037797)
> Lack of security updates past 2019 forced our hand. Did you find a way around that?

Amazon is maintaining Python 2 for at least 4 years, as part of their Amazon Linux long term support release. Google app engine will support Python 2 for an unknown amount of time; they haven't announced an end date. PyPy is Python 2, with (to the best of my limited knowledge) no plans to deprecate support. There are also other LTS releases out there which include Python 2 support.

IOW, the forcing function of the PSF no longer supporting Python is not as big a factor as was hoped.

Re:Mercurial’s journey to and reflections on Python 3 by rst on Monday January 13, 2020 @04:32PM (#22038882)
Security updates in Python itself aren't the only issue; a Python 2 project may also depend on packages with security issues of their own, which require continued upstream maintenance.

For example, the python-saml package (for managing SAML-based single sign-on) has separate Python 2 and Python 3 versions, and implements a security-sensitive protocol which means it has (in the fairly recent past) gotten security updates for issues serious enough to rate an assigned CVE. If you're using it, having the current maintainers walk away from the Python 2 version is a serious risk...

Re:Mercurial’s journey to and reflections on Python 3 by jnwatson on Monday January 13, 2020 @05:07PM (#22039253)
I'm a maintainer for a somewhat popular Python package that had support all the way back to 2.4, but I've had to systematically remove support for those versions. The problem is all the CI infrastructure and testing packages are removing support.

Is Amazon planning to support pytest for at least 4 years? It will have its last 2.7-supporting release very soon.

Re:Mercurial’s journey to and reflections on Python 3 by viraptor on Monday January 13, 2020 @03:25PM (#22038212)
This would only help the server side of mercurial though. There's no client-side supported distribution really. Pypy is not that popular yet.
Re:Mercurial’s journey to and reflections on Python 3 by falcolas on Monday January 13, 2020 @03:51PM (#22038424)
I don't know about others, but when I used Mercurial, it was via installing it through brew. And if brew installed pypy as a dependency so Mercurial could still use Python 2, I probably wouldn't have noticed.
Re:Mercurial’s journey to and reflections on Python 3 by viraptor on Monday January 13, 2020 @08:58PM (#22041098)
You'd notice, because it wouldn't work: https://www.mercurial-scm.org/wiki/PyPyPlan