On Tue, Mar 2, 2021 at 4:30 AM Matthias Klose <d...@debian.org> wrote: > On 2/16/21 5:34 PM, Zack Weinberg wrote: > > Unpackaged Python-2-only software > > will continue to exist indefinitely—I am *certain* that I will still > > need a Python 2 interpreter ten years from now, and I fully expect my > > grandchildren will occasionally trip over Python-2-only software even > > a hundred years from now. > > Please also consider the burden on other grandparents having to explain their > grandchildren that they have to type "python3" on Debian, when anybody else > running Python on a different platform or running Python on other Linux > distributions is used to type "python" ;)
I sincerely hope that the organizations shipping Python 3 as "python" will come to their senses in the near future and stop doing so, so everyone will in fact be used to typing "python3". > I don't think there's a good solution for everybody. I still think it's > better > to provide an explicit choice in a package, instead of following instructions > from the web to manage the "python" symlink using update-alternatives. That's all well and good, but I do not think the choice represented by "python-is-python3" should be offered as an option. The change I am asking for is the removal of this package from Debian, and I think it is _especially_ important that this package not be included in bullseye (as this will be the first release without Python 2, AIUI). > I'm going to propose an addition to the Debian Python Policy on the > debian-python ML: [...] I like this except for the part that implies "python-is-python3" will be an option. zw
