Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: Discussing next steps for the Python2 removal Date: Fri, 25 Oct 2019 03:40:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 25 01:30:07 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.65 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-qk1-f174.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=HrKbaz3JTei1AVDJxz5XGusec5LSNWDfyXAkgoHIbeM=; b=q23ioxAf2fRL6D46DXFqQX955qNrohPTcwUPQe/KvN/mKaCqiMUfTSadXUvi2Gyoob PebaGexk/RupEXpiEt1jP3yyvRcHNCfz1sgNn2Hhlo2C+s8iu+QJ0q1hd3aXtTaiBD3r /OiuGGdLJHEpIeLTJdlPfEhncEnfaqT7nDBiIirFMGsTAV6HrfRnT+bdfUo27HqdheBj e5LE+waCpySNVCJ0Dc7sX4dW6HCTUJLEe1CJSpVJ6lop16Nz/WnD1luWbBYOqfRhKnqg 39A2WUqcK4fpAUXD50/MKoLrpj8kfmyfWP8PB/4a0PRYmDrAMvDuOa2h020G6oxDVUCJ 7PcA== X-Gm-Message-State: APjAAAXbyNVNLmeaIM3dBOkui8PY9l8hTpqJRnPG25fxcuORrEfuO9gr cOdaaJOcgo3Wouz9AaFWO4cH8TFipVDp/khrFtfUJrek4K7gYA== X-Google-SMTP-Source: APXvYqwIa0x4r1RWu7NuBF8hpwkbzXgKA9m3mseRkB4ND6u3gfMI4leCBD2xT1tw6EaCjWY9vgyjDlX1I5n4RyIDdzo= X-Received: by 2002:a37:7906:: with SMTP id u6mr715947qkc.5.1571966990616; Thu, 24 Oct 2019 18:29:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/17498 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXx5R3uEkLz7iLjGX-ZTZivWnKTVnJPk3NDQGYtBrO96Jg@mail.gmail.com Approved: robomod@news.nic.it Lines: 59 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Matthias Klose , Paul Gevers , Chris Lamb X-Original-Date: Thu, 24 Oct 2019 21:29:24 -0400 X-Original-Message-ID: X-Original-References: <10ee755b-5e97-84bc-22d8-4ed29182bf84@debian.org> Xref: csiph.com linux.debian.maint.python:11938 On Thu, Oct 24, 2019 at 4:09 PM Ondrej Novy wrote: > We want to bump all bugs to RC bugs, if they are: Was there anyone from the RT that ack'd this? Paul is here and i guess he can do that now: there could be hundreds of new RC bugs in a blink. > * leaf package > * with py2 binary do we really want to remove from testing (and subsequently from debian, as mentioned below) if it both has a py2 and a py3k package? should we limit this to py2-ONLY packages? > * bug is not marked as py2keep > * all modules and low popcon apps (< 300) JFYI for now i was steering clear of removing py2 support even of modules with high popcon (while it's true they may not have any rdeps in the archive, there could be plenty of 3rd party code using them). > If package will be removed from testing (auto-rm), we are going to remove= them from unstable. We are going to run this process semi-automatically (a= fter more packages gets leaf). First version of list should be checked (ema= iled to this ML). We need to prepare draft of RC-bumper email. mailing an explanation can be tricky: currently the script simply generates a mail to control@ and that's usually accepted within seconds of it sending it. but the BTS mail server do implement greylisting and throttling so generating a huge number of individual emails could just result in them being queued on my machine until accepted, and make the script generate duplicate emails (possibly confusing the end users and definitely un-necessary). we could go with multi-recipients emails, but first we need to identify how many recipients is acceptable for the BTS mail severs (there are usually rules in place to prevent spam), and that also means there will be a rather long "control header" (for the control commands) in the email, rendering rather ineffective the text of the explanation, which will be at the bottom. > We will send email to d-d-a with current state, our next steps, etc. > > We are going to bump Lintian tags severity: > * python-foo-but-no-python3-foo: warning->error > * dependency-on-python-version-marked-for-end-of-life: pedantic->warning > * new-package-should-not-package-python2-module: warning->error > * build-depends-on-python-sphinx-only: warning->error > * depends-on-python2-and-python3: info->warning > * script-uses-unversioned-python-in-shebang: info->warning is there any plan to make some of this tags an upload-rejecting one? thanks everyone on working to get rid of python2 from debian! --=20 Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi