Re: Reaching team consensus on usage of py3versions -r and X-Python3-Version in Lintian
> 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
> <em>requested</em> by your sources with the command <code>py3versions
> --requested</code> but your sources do not actually declare those
> versions with the field <code>X-Python3-Version</code>.
> .
> Please query all <em>supported</em> Python versions with the command
> <code>py3versions --supported</code> in your test instead.
>
> 2. Change the desc for tag query-requested-python-versions-in-test to
>
> The specified test queries all <em>supported</em> Python versions with
> the command <code>py3versions --supported</code> but your sources
> request a specific set of versions via the field
> <code>X-Python3-Version</code>.
> .
> Please delete the field <code>X-Python3-Version</code>, 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
Reply to: