Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!feeds.phibee-telecom.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Diane Trout Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: Python louvain packages naming confusion. Date: Wed, 10 Feb 2021 05:30:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Feb 10 04:24:25 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.57 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, LDO_WHITELIST=-5, RDNS_NONE=0.793, SARE_MSGID_LONG40=0.637] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/18966 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/619595d566340c72c355fe7c283bcfe8096f49e7.camel@ghic.org Approved: robomod@news.nic.it Lines: 70 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, debian-med@lists.debian.org, 982417@bugs.debian.org X-Original-Date: Tue, 09 Feb 2021 20:24:02 -0800 X-Original-Message-ID: <619595d566340c72c355fe7c283bcfe8096f49e7.camel@ghic.org> X-Original-References: Xref: csiph.com linux.debian.maint.python:13184 linux.debian.bugs.dist:1047393 On Wed, 2021-02-10 at 01:49 +0000, Paul Wise wrote: > On Tue, Feb 9, 2021 at 10:21 PM Diane Trout wrote: > > > The fairly popular (in the world of bioinformatics) ScanPy package > > uses > > a Python version of the louvain clustering algorithm implemented > > by: > ... > > However currently in the Debian archive there's a different louvain > > package > > I think this is something that the two upstream projects should > discuss and come to an agreement on the right outcome, since the > current set of names is confusing and overlapping. Perhaps the two > projects will end up getting merged into one project, or one of them > deprecated or one or both of them renamed. >From the perspective of pypi. One is "louvain" (which installs into "louvain" and one is "python- louvain", which installs into "community". If you're using pip you can easily install both of them if you want. > > > 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. > > There are no reverse dependencies in Debian, but this is going to be > tricky for users who previously installed python3-louvain.deb from > python-louvain upstream and then after upgrading they suddenly get > python3-louvain.deb from louvain-igraph with presumably an > incompatible API etc. > Cleaning it up seemed hard. Currently the version python3-louvain in unstable based on python- louvain is 0.0+20181013git3fc1f575 and the current upstream version is 0.15. For the louvain igraph package their current version is 0.7.0. At the very least, the current python3-louvain package needs to be renamed to python3-community to meet python policy and to make the CI autodep8 import test work. So that seems like make a new release of python-louvain using the 0.0git convention with a transition package that depends on a new python3-community package. And then leave that alone for "a while". At some point then the new python3-louvain package based on the louvain igraph module could have a check in the maintainer script to tell the user to switch to python3-community if it's the older python-louvain version. Once the packages are renamed then the python-louvain version could switch from the 0.0git convetion to the pypi version. (Upstream didn't bother to put tags on github, so the only version numbers come from pypi). I have no idea how long the transition package should sit around for though. Diane