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

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

Bug#982417: Python louvain packages naming confusion.

Cross-posted to 2 groups.

Show key headers only | View raw

On Wed, 2021-02-10 at 18:35 -0500, Sandro Tosi wrote:
> +Steffen explicitly, given the team is not in Maintainer nor
> Uploaders
> 
> > How about renaming the current python3-louvain package to
> > python3-community-louvain using a normal transition package.
> 
> that's incorrect: src:python-louvain builds a module called
> `community` (that includes also a cli tool), so the resulting binary
> package should either be `python3-community` or `community` where the
> cli is the main product and the module is installed in /usr/share/ to
> support it.
> 

It is bending policy, but I liked python3-community-louvain because the
package name "python3-community" is just an exceptionally vague name. I
think it's clearer if the name of the algorithm is in the package name.

Also while looking through scanpy's louvain function I learned of yet
more implementations of louvain. (Look through this function for
different "flavors")
https://github.com/theislab/scanpy/blob/550b82fdb53f35890e60343b826dd19454600bdb/scanpy/tools/_louvain.py#L23

Apparently what I'd previously called "igraph", scanpy calls "vtraag"
because the vtraag version builds on the louvain implementation
in python-igraph.

There's also yet another version in nvidia's rapids library.

> > Then I can submit the other louvain package using a binary package
> > name
> > of python3-louvain-igraph.
> 
> this is incorrect too: (perspective) src:louvain (or
> src:louvain-igraph, as the upstream called their repo) builds a
> module
> called `louvain` so the resulting binary package should be
> `python3-louvain` eventually conflicting with the existing package
> (<<
> current-version-in-sid)
> 
> src:python-louvain is in a pretty bad shape: it received a single
> upload in late 2018, it has an RC bug since a *day* after that
> upload,
> and it has never been in testing: tbh i dont consider this package to
> be maintained/targeting any stable release, so i believe you can
> "take
> over" the namespace given you seem to show interest in maintaining
> https://github.com/vtraag/louvain-igraph

I wasn't sure how much effort to put into saving the previous Debian
louvain package since it didn't look like it was really usable by
anyone.

Libraries.io makes it look like the python-louvain "import community"
version is a bit more popular and more actively developed. The "vtraag"
version has a comment in it's REAME saying the developer deprecated it
in favor of leidenalg (an improved method).

On the other hand scanpy thinks the vtraag version is the most feature
full implementation of louvain and uses it as their default.

Diane

Back to linux.debian.maint.python | Previous | Next — Previous 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