Path: csiph.com!4.us.feeder.erje.net!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod From: Simon McVittie Newsgroups: linux.debian.maint.python Subject: Re: autopkgtest-pkg-python fails if package name is python-pyMODULENAME (Was: Bug#945768: python-pypubsub: autopkgtest failure: No module named 'pypubsub') Date: Thu, 28 Nov 2019 18:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Nov 28 17:28:13 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.801 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FROM_FMBLA_NEWDOM=1.499, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.12.2 (2019-09-21) X-Mailing-List: archive/latest/17660 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20191128172753.GA383286@espresso.pseudorandom.co.uk Approved: robomod@news.nic.it Lines: 42 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 28 Nov 2019 17:27:53 +0000 X-Original-Message-ID: <20191128172753.GA383286@espresso.pseudorandom.co.uk> X-Original-References: <20191128150402.GK2400@an3as.eu> <20191128161129.GL2400@an3as.eu> Xref: csiph.com linux.debian.maint.python:12058 On Thu, 28 Nov 2019 at 11:15:31 -0500, Sandro Tosi wrote: > if you install `pubsub` as top-level module, your package must be > named pythonN-pubsub, if not it violates the policy and it's RC buggy. That's what I had thought, but I've also seen people asserting that the Debian package name ought to reflect the egg name in cases where it differs from the top-level Python module name. Some examples of where the difference between egg name and module name matters: - this one: - module: pubsub (-> python3-pubsub) - egg: pypubsub-*.egg-info (-> python3-pypubsub) - is actually python3-pypubsub (named for the egg) - src:dbus-python: - module: dbus (-> python3-dbus) - egg: dbus_python-1.2.14.egg-info (-> python3-dbus-python) - is actually python3-dbus (named for the module) - src:pygobject: - module: gi (-> python3-gi) and pygtkcompat - egg: PyGObject-3.34.0.egg-info (-> python3-pygobject) - is actually python3-gi (named for the module) (Maybe python3-gi should also have Provides: python3-pygtkcompat?) Is there consensus that the top-level module name is what matters, and not following the recommendation is a bug? https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html says "The binary package for module foo should preferably be named python3-foo, if the module name allows" and "import foo should import the module", which suggests that it is indeed the name of the top-level importable module, and not the name of the egg, that matters (which would imply that -dbus and -gi are correct, and -pypubsub is not). Is there consensus that not following this recommendation is a *RC* bug? The bits I quoted above say "should" rather than "must". Thanks, smcv