Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= Newsgroups: linux.debian.maint.python Subject: Re: Python 2 support for Bullseye Date: Sun, 15 Nov 2020 19:10:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Nov 15 18:03:51 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.54 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, SARE_MLH_Stock10=1.66] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/18777 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20201115180335.GA792205@pisco.westfalen.local Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 15 Nov 2020 19:03:35 +0100 X-Original-Message-ID: <20201115180335.GA792205@pisco.westfalen.local> X-Original-References: <20201016180456.GA21493@pisco.westfalen.local> <3422840e-8a2b-85f8-8b79-2ae323c60542@debian.org> Xref: csiph.com linux.debian.maint.python:13012 > 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