Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
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 21:50:01 +0100
Message-ID: <z7yTD-7ec-5@gated-at.bofh.it>
References: <z7tAB-44m-1@gated-at.bofh.it> <z7u3E-4eC-5@gated-at.bofh.it> <z7uGl-4Ii-1@gated-at.bofh.it> <z7uGl-4Ii-5@gated-at.bofh.it> <z7vM5-5m7-13@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 56
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12063



On November 28, 2019 5:27:53 PM UTC, Simon McVittie <smcv@debian=2Eorg> wr=
ote:
>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=2E
>
>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=2E
>
>Some examples of where the difference between egg name and module name
>matters:
>
>- this one:
>  - module: pubsub (-> python3-pubsub)
>  - egg: pypubsub-*=2Eegg-info (-> python3-pypubsub)
>  - is actually python3-pypubsub (named for the egg)
>
>- src:dbus-python:
>  - module: dbus (-> python3-dbus)
>  - egg: dbus_python-1=2E2=2E14=2Eegg-info (-> python3-dbus-python)
>  - is actually python3-dbus (named for the module)
>
>- src:pygobject:
>  - module: gi (-> python3-gi) and pygtkcompat
>  - egg: PyGObject-3=2E34=2E0=2Eegg-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=2Edebian=2Eorg/doc/packaging-manuals/python-policy/module_pac=
kages=2Ehtml
>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)=2E
>
>Is there consensus that not following this recommendation is a *RC*
>bug?
>The bits I quoted above say "should" rather than "must"=2E
>
>Thanks,
>    smcv

Python Policy is not Debian Policy=2E  It's not a "policy" violation in th=
e sense of a serious bug=2E  That said, it would be better to change it=2E

Scott K