Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.maint.python Subject: Re: Python 2 support for Bullseye Date: Fri, 16 Oct 2020 20:30:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 16 18:21:26 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.153 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, NICE_REPLY_A=-0.213, RCVD_IN_DNSWL_LOW=-0.7, SARE_MLH_Stock10=1.66] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 Old-X-Envelope-From: doko@debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/18709 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/3422840e-8a2b-85f8-8b79-2ae323c60542@debian.org Approved: robomod@news.nic.it Lines: 39 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 16 Oct 2020 20:21:09 +0200 X-Original-Message-ID: <3422840e-8a2b-85f8-8b79-2ae323c60542@debian.org> X-Original-References: <20201016180456.GA21493@pisco.westfalen.local> Xref: csiph.com linux.debian.maint.python:12949 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. > but exempt it from support (and then > remove it for good after the Bullseye release): not ok. That would mean removing pypy3 from the archive as well. If you don't want to support Python2, then why do you care about it's removal for bullseye+1? > - Mark src:python (plus related support packages) as unsupported in > debian-security-support and with a README.Debian in the source > package (and given how prominent Python is, also in the release notes) That should list the binary packages, there's no src:python package. > - Bump the severity of the few remaining packages in testing to RC > state (and force them out testing if auto removals were blocked > for some reason) See above, I think it's unfriendly to push out pypy3. Matthias