Re: Python2 packages for bullseye
On 7/9/20 1:45 PM, Scott Kitterman wrote: > On Thursday, July 9, 2020 7:21:45 AM EDT Matthias Klose wrote: >> The removal of packages still depending on Python2 looks good [1], however >> we have a bunch of packages that still require Python2, and where >> maintainers explicitly asked to keep those in the distro [2]. Among those >> are pypy and pypy3 which need Python2 for bootstrapping. I'm going to keep >> the Python2 packages for bullseye, and having those just as build >> dependencies shouldn't really effect any end-user. A different thing might >> be the Python2 usage at runtime, however I'm not very passionate to remove >> all of those packages. >> >> What still should be done for bullseye is the removal of the unversioned >> python. I'm removing the packages python-minimal, python, python-dev, >> python-dbg, python-doc, and stop shipping the /usr/bin/python symlink, so >> that packages are required to either use python2 or python3 explicitly. >> Planning that change for late August / early September. That should give >> plenty of time to address any unversioned python usage before the release >> freeze. > > Are you going to keep python-setuptools? If you do, it seems likely we'll be > able to keep pip and virtualenv so they support running python2 in a > virtualenv in bullseye, which seems the best way to do it for those that need > to. yes, that would be a sensible thing to do.
Re: Python2 packages for bullseye
On Thursday, July 9, 2020 7:21:45 AM EDT Matthias Klose wrote: > The removal of packages still depending on Python2 looks good [1], however > we have a bunch of packages that still require Python2, and where > maintainers explicitly asked to keep those in the distro [2]. Among those > are pypy and pypy3 which need Python2 for bootstrapping. I'm going to keep > the Python2 packages for bullseye, and having those just as build > dependencies shouldn't really effect any end-user. A different thing might > be the Python2 usage at runtime, however I'm not very passionate to remove > all of those packages. > > What still should be done for bullseye is the removal of the unversioned > python. I'm removing the packages python-minimal, python, python-dev, > python-dbg, python-doc, and stop shipping the /usr/bin/python symlink, so > that packages are required to either use python2 or python3 explicitly. > Planning that change for late August / early September. That should give > plenty of time to address any unversioned python usage before the release > freeze. Are you going to keep python-setuptools? If you do, it seems likely we'll be able to keep pip and virtualenv so they support running python2 in a virtualenv in bullseye, which seems the best way to do it for those that need to. Scott K signature.asc Description: This is a digitally signed message part.
