Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: =?utf-8?Q?"Yao_Wei_=28=E9=AD=8F=E9=8A=98=E5=BB=B7=29"?= <mwei@debian.org>
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: Fri, 29 Nov 2019 01:40:01 +0100
Message-ID: <z7Cud-13J-1@gated-at.bofh.it>
References: <z7vM5-5m7-13@gated-at.bofh.it>
X-Original-To: Simon McVittie <smcv@debian.org>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Fri Nov 29 00:30:37 2019
Old-Return-Path: <mwei@debian.org>
X-Amavis-Spam-Status: No, score=-4.098 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, FROM_FMBLA_NEWDOM=1.499, HTML_MESSAGE=2, LDO_WHITELIST=-5, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=no autolearn_force=no
X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .relay1-d.mail.gandi. - helo-domain: .gandi.)  FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5
X-Originating-IP: 223.136.65.218
Content-Type: multipart/alternative; boundary=Apple-Mail-F2EB9520-064D-4432-B7FD-E85E5F580295
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (17B111)
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/17666
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/BEE25698-82FD-4368-B094-D3016A121337@debian.org
Approved: robomod@news.nic.it
Lines: 68
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Cc: debian-python@lists.debian.org
X-Original-Date: Fri, 29 Nov 2019 08:30:16 +0800
X-Original-Message-ID: <BEE25698-82FD-4368-B094-D3016A121337@debian.org>
X-Original-References: <20191128172753.GA383286@espresso.pseudorandom.co.uk>
Xref: csiph.com linux.debian.maint.python:12064


--Apple-Mail-F2EB9520-064D-4432-B7FD-E85E5F580295
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable


> On Nov 29, 2019, at 01:28, Simon McVittie <smcv@debian.org> wrote:
>=20
> 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).

If the module name has upper case in it, it would actually break Policy =C2=A7=
5.6.1

For example one of my package has module name fontParts, and if folllowing P=
ython policy, the name would be python3-fontParts, and it would be a policy v=
iolation.

So it has to be using all lower-case name, therefore running tests generated=
 by autopkgtest fails.  I have to generate the testing script manually and m=
odify accordingly.

Yao Wei

(This email is sent from a phone; sorry for HTML email if it happens.)


--Apple-Mail-F2EB9520-064D-4432-B7FD-E85E5F580295
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><br><div dir=3D"ltr"><blockquote type=3D"ci=
te">On Nov 29, 2019, at 01:28, Simon McVittie &lt;smcv@debian.org&gt; wrote:=
<br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr"><span></sp=
an><br><span>Is there consensus that the top-level module name is what matte=
rs, and not</span><br><span>following the recommendation is a bug?</span><br=
><span>https://www.debian.org/doc/packaging-manuals/python-policy/module_pac=
kages.html</span><br><span>says "The binary package for module foo should pr=
eferably be named</span><br><span>python3-foo, if the module name allows" an=
d "import foo should import</span><br><span>the module", which suggests that=
 it is indeed the name of the top-level</span><br><span>importable module, a=
nd not the name of the egg, that matters (which would</span><br><span>imply t=
hat -dbus and -gi are correct, and -pypubsub is not).</span><br></div></bloc=
kquote><div><br></div><div>If the module name has upper case in it, it would=
 actually break Policy =C2=A75.6.1</div><div><br></div><div>For example one o=
f my package has module name fontParts, and if folllowing Python policy, the=
 name would be python3-fontParts, and it would be a policy violation.</div><=
div><br></div><div>So it has to be using all lower-case name, therefore runn=
ing tests generated by autopkgtest fails. &nbsp;I have to generate the testi=
ng script manually and modify accordingly.</div><div><br></div><div>Yao Wei<=
/div><div><div dir=3D"ltr"><div><br></div><div>(This email is sent from a ph=
one; s<span style=3D"background-color: rgba(255, 255, 255, 0);">orry for HTM=
L email if it happens.</span><span style=3D"font-size: 13pt;">)</span></div>=
<div><span style=3D"font-size: 13pt;"><br></span></div></div></div></body></=
html>=

--Apple-Mail-F2EB9520-064D-4432-B7FD-E85E5F580295--