Hi Matthias (2025.03.06_03:58:25_-0400)
No, the root cause is with the proposed solution, you have hard coded dependencies on all python3.x versions, forcing installation of these. Which is not what I would like to have.

Let me expand on this a little:

tk and gdbm are stdlib modules that we make optional in Debian, shipping them in separate binary packages.

Packages that need gdbm or tk depend on python3-gdbm and python3-tk, as if they were 3rd party python libraries.

python3-gdbm (for example) depends on "python3.12-gdbm, python3.13-gdbm" (before the 3.13-only transition). This gives the same result as would be expected for a 3rd party python library: the module is available for all supported python3 versions. It just happens to have been achieved via binary packgages built in the python3.12 and python3.13 source packages.

If we added the dependencies you propose, then installing python3-gdbm would necessarily install all supported python versions. This isn't desired.

Stefano

--
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Reply via email to