Package: python3-louvain
Version: 0.0+20181013git3fc1f575-1
Severity: serious
Justification: Python packaging 3.3 Module Package Names

Dear Maintainer,

According to Section 3.3 of the Python Policy package binary names should match
their import names:
https://www.debian.org/doc/packaging-manuals/python-
policy/module_packages.html#package_names

"For the purposes of package naming, the name that is used for a module is the
name that can be used with import, which is not necessarily the same as the
name used in setuptools PKG-INFO and .egg-info files and directories. For
example, the module described in pyxdg-*.egg-info is used via import xdg, so
its package name is python3-xdg and not python3-pyxdg."

Also the autodep8 tests fail because the package name doesn't match the import
name.

"Testing with $py:" ; $py -c "import louvain; print(louvain)" ; done
autopkgtest [13:29:03]: test autodep8-python3: [-----------------------
Testing with python3.9:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'louvain'




-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-debug'), (500, 'testing'), 
(500, 'stable'), (110, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-louvain depends on:
ii  python3           3.9.1-1
ii  python3-networkx  2.5+ds-2

python3-louvain recommends no packages.

python3-louvain suggests no packages.

Reply via email to