Path: csiph.com!news.mixmin.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Re: Reaching team consensus on usage of py3versions -r and X-Python3-Version in Lintian Date: Mon, 17 Jan 2022 21:00:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jan 17 19:54:57 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.501 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, 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-ed1-f51.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AOAM533q13h2mU8McI7sZtGVsB/4JDokiwNk4ttRK2IMICjeOCe7m2Mr SJaYaIlcGSHgeUbu9t2QnfyuTG8OQDFvA5YlJPMhVSKzCfU= X-Google-SMTP-Source: ABdhPJyC/KLtEcEr7h6/aLLRdD9bLtrKfrtKy6mbIssHFmzrGf003iRlKRMntTnTikHLW/Punda5kheuni6NpakDMV8= X-Received: by 2002:a17:906:11da:: with SMTP id o26mr9722793eja.379.1642449281326; Mon, 17 Jan 2022 11:54:41 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/19702 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXyAo3ugcHtsfh_Qr1AApgU31ukDFnD-2PCtkax6q9ehVg@mail.gmail.com Approved: robomod@news.nic.it Lines: 43 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 17 Jan 2022 14:54:14 -0500 X-Original-Message-ID: X-Original-References: X-Received-Bytes: 3922 Xref: csiph.com linux.debian.maint.python:13889 > I think the proper fix would be to ask people to move away from > `py3versions -r` if there is no X-Python3-Version, and use`py3versions > -s` instead. > > As such, I think we should ask the Lintian maintainers to: > > 1. Change the desc for tag declare-requested-python-versions-for-test to > > The specified test attempts to query the Python versions > requested by your sources with the command py3versions > --requested but your sources do not actually declare those > versions with the field X-Python3-Version. > . > Please query all supported Python versions with the command > py3versions --supported in your test instead. > > 2. Change the desc for tag query-requested-python-versions-in-test to > > The specified test queries all supported Python versions with > the command py3versions --supported but your sources > request a specific set of versions via the field > X-Python3-Version. > . > Please delete the field X-Python3-Version, as it is not needed. +1 > AFAIU, the only valid use of X-Python3-Version would be a package that > fails to build on an older but currently supported version of Python > (let's say 3.9) but builds on the newer version (say 3.10). I think such > use cases are pretty rare though. maybe https://www.debian.org/doc/packaging-manuals/python-policy/#specifying-supported-versions would need to be updated to clarify that the optional field is meant to be used in exceptional circumstances (and state what they are explicitly) and we generally expect the field to be absent. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi