[Python-modules-team] Bug#965290: mercurial-keyring: binary package name doesnt follow Python Policy

[Sandro Tosi]

Package: mercurial-keyring
Severity: important

Hello,
as stated in the python policy, packages that provide python modules (ie
something you `import xxxx`), they must have their binary package name with a
`python3-` prefix; src:mercurial-keyring simply provide a binary pkg
named `mercurial-keyring`; please fix.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mercurial-keyring depends on:
ii  mercurial                  5.4.1-2
pn  mercurial-extension-utils  <none>
ii  python3                    3.8.2-3
ii  python3-keyring            17.1.1-1

mercurial-keyring recommends no packages.

mercurial-keyring suggests no packages.