3 ms·
The normal thing in Debian is for a maintainer who wants to step down to orphan the package so that other maintainers get the chance to pick it up. It seems pe
by mjw1007 7y ago
The normal thing in Debian is for a maintainer who wants to step down to orphan the package so that other maintainers get the chance to pick it up.
It seems perfectly reasonable for the Debian Python team to decide they no longer want Python 2 getting in their way. But I think they should have done more to check whether someone else wants to take over.
There's nothing terribly wrong with packaging mature software that doesn't have an active upstream. Realistically nobody cares about any remaining bugs in Python 2 being fixed; the work involved would basically be making sure it still compiles with newer versions of GCC.
- Beltiras 7y agoThere are 5 CVEs for 2.7 so far in 2019 [1]. [1]: https://www.cvedetails.com/vulnerability-list/vendor_id-10210/product_id-18230/version_id-92056/year-2019/Python-Python-2.7.html https://www.cvedetails.com/vulnerability-list/vendor_id-1021...
- mjw1007 7y agoYes, I think whoever ends up taking over Python 2 maintenance would be well advised to stub out the https support immediately, and maybe a bit later do the same for all support for network requests. In particular, you don't want to have to worry about building against openssl. I think the vast majority of cases where people have a good reason to carry on using Python 2 won't need that.