> On 10/16/20 8:04 PM, Moritz Mühlenhoff wrote:
> > There will be few core packages build-depending on Python 2 (for tests
> > or building) which won't be ready for Python 3 for Bullseye (Chromium,
> > qtwebkit and IIRC also Pypy), but those only need Python 2 (and a very
> > small set of support packages like setuptools/jinja) to build and
> > run their tests.
> >
> > Apart from those there's only a handful of packages still in testing
> > which have a run time dependency on Python 2 packages (and most are
> > actively being worked on (e.g. Xen)).
> >
> > All packages (and their test suites) shipped in Debian are trusted
> > anyway (and consequently don't need any kind of updates during the
> > bullseye cycle), so a lack of updates/upstream EOL doesn't matter.
> >
> > As such, I'd propose to include Python 2 (plus the small set of
> > support packages) in Bullseye
>
> ok. I think you should explicitly name all these packages.
I'll file a bug against debian-security-support to list cython, python2.7
and python-stdlib-extensions as unsupported except for building (these
are Py2-only and debian-security-support only operates on source packages,
so we can't mark binary packages like python-setuptools, but that's fine.
In addition I'm planning to submit the following for release notes:
| Debian Bullseye includes a version of Python 2.7 (and a short list of
| related packages like setuptools still built Python 2 packages). However,
these
| are only included for building a few applications which still require
| Python 2 as part of their build process. Python 2 is not supported for
| running applications and there won't be any security updates for Python
| 2 in Bullseye.
Cheers,
Moritz
