Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13182

Python louvain packages naming confusion.

From Diane Trout <diane@ghic.org>
Newsgroups linux.debian.maint.python, linux.debian.bugs.dist
Subject Python louvain packages naming confusion.
Date 2021-02-09 23:30 +0100
Message-ID <BGJG9-6Wa-1@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Hello,

The fairly popular (in the world of bioinformatics) ScanPy package uses
a Python version of the louvain clustering algorithm implemented by:

https://github.com/vtraag/louvain-igraph
https://pypi.org/project/louvain/

which installs into the "louvain" dist-packages directory.
(from debc)
./usr/lib/python3/dist-packages/louvain/

I have it mostly packaged 

However currently in the Debian archive there's a different louvain
package 

https://github.com/taynaud/python-louvain
https://pypi.org/project/python-louvain/
https://salsa.debian.org/python-team/packages/python-louvain

It installs into (according to debc)
./usr/lib/python3/dist-packages/community/

Unfortunately for this package we now automatically run autodep8 which
fails because the import name is community and not louvain.

autopkgtest [13:29:03]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo
"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'
autopkgtest [13:29:03]: test autodep8-python3: -----------------------]
autopkgtest [13:29:03]: test autodep8-python3:  - - - - - - - - - -
results - -


I think having a python3-louvain-igraph package which installs into
louvain, while there is a separate python3-louvain package which
installs into community is really confusing.

I was wondering if the python3-louvain's binary package should be
renamed to python3-community to match the python package name, and then
the other louvain-igraph package could provide a bin package named
python3-louvain which would match the package name.

But this is clearly a thing that needs to be discussed.

Diane

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-09 23:30 +0100
  Re: Python louvain packages naming confusion. Paul Wise <pabs@debian.org> - 2021-02-10 02:50 +0100
    Re: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 05:30 +0100
  Re: Python louvain packages naming confusion. "Michael R. Crusoe" <crusoe@debian.org> - 2021-02-10 10:50 +0100
    Bug#982417: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 19:40 +0100
    Re: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 21:30 +0100
      Re: Python louvain packages naming confusion. Sandro Tosi <morph@debian.org> - 2021-02-11 00:40 +0100
        Bug#982417: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-11 02:00 +0100

csiph-web