[Debian-astro-maintainers] Bug#1085728: python-multipart: Make room for https://pypi.org/project/multipart/ somehow?

[Thomas Goirand]

On 11/6/24 19:17, Simon McVittie wrote:
> On Wed, 06 Nov 2024 at 18:00:43 +0000, Colin Watson wrote:
>>   * Rename python-multipart source package to python-python-multipart,
>>     and its binary package to python3-python-multipart.  Yes, it's a bit
>>     ugly, but there are currently 13 other binary packages in the archive
>>     whose names start with "python3-python-", so there's precedent, and
>>     it matches the way we usually transform PyPI names into Debian
>>     package names.
> 
> The policy says we do not transform PyPI names into Debian package names
> (or at least, not binary package names). Instead, we transform the name
> that you can `import` into a Debian binary package name.

The policy is arguably completely wrong. What we should be doing, is 
using the Python egg-name as package name instead, so that we have a 
chance for the package dependency to be well calculated. If upstream 
doesn't have egg-name == PyPi name, then I consider this a bug upstream 
that should deserve fixing.

Instead, the policy mandates the wrong thing, which makes us use stupid 
renaming during package dependency calculating, with a list of fixups 
that is eventually badly maintained. For this reason, I never trust 
dh-python to make the correct work, and I always express the 
dependencies manually in debian/control myself.

So, the (arguably wrong) Python policy isn't a point of argumentation, 
especially here. :)

> But if src:python-multipart is moving towards the name that you should
> canonically import being `python_multipart`, then its correct binary
> package name would be python3-python-multipart anyway.
> 
>      smcv

Anyways I agree with what Colin wrote, and python3-python-multipart is 
ok to me, especially considering this matches both egg-name and module 
import name.

Cheers,

Thomas Goirand (zigo)