Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Piotr =?utf-8?Q?O=C5=BCarowski?= <piotr@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Python/LibraryStyleGuide: Executables and library packages dokonana  przez BarryWarsaw
Date: Wed, 07 Oct 2015 23:40:02 +0200
Message-ID: <qh4Bk-eo-15@gated-at.bofh.it>
References: <qh4Bk-eo-17@gated-at.bofh.it>
Old-Return-Path: <ozarow@gmail.com>
Sender: robomod@news.nic.it
Mail-Followup-To: debian-python@lists.debian.org
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="mSxgbZZZvrAyzONB"
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Approved: robomod@news.nic.it
Lines: 86
Organization: linux.* mail to news gateway
Xref: csiph.com linux.debian.maint.python:7544


--mSxgbZZZvrAyzONB
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[Debian Wiki, 2015-10-07]
> https://wiki.debian.org/Python/LibraryStyleGuide?action=3Ddiff&rev1=3D64&=
rev2=3D65
>=20
>  =20
>   =3D=3D Gotchas =3D=3D
>  =20
> + =3D=3D=3D Executables and library packages =3D=3D=3D
> +=20
> + Let's say you have a Python package which results in Python 2 and 3 lib=
raries, and a Python 3 executable.  What is the best practices for naming a=
nd organizing your binary packages?
> +=20
> + Clearly you want to have:
> +=20
> +  * python-foo -- the Python 2 library
> +  * python3-foo -- the Python 3 library

     * foo -- for the executable (and possible additional dependencies that=
 library doesn't need)

maybe extent it to:

     * python-foo -- the Python 2 library (and Python 2.X scripts if they'r=
e Python 2.X specific)
     * python3-foo -- the Python 3 library (and Python 3.X scripts if they'=
re Python 3.X specific)

> +=20
> + but where should the `/usr/bin/foo` script go?  You could put it in `py=
thon3-foo` but you '''CANNOT''' put it in `python-foo` or for that matter a=
ny binary package that starts with the `python-` prefix.  `dh_python3` refu=
ses to rewrite shebang lines for any executable in a binary package that st=
arts with "python-" or "pypy-".  This means that something like `python-foo=
-cli` or `python-foo-bin` is unacceptable.

I'd remove this part - it's not dh_python3 specific (dh_python2 and
dh_pypy does similar things) and I don't think such corner case should
be in style guide

> +=20
> + Here are some recommendations.  We do not have a standard (though maybe=
 we should):
> +=20
> +  * `foo` - this is nice if it parallels the /usr/bin/foo name but it mi=
ght collide with existing packages, and some people don't like to make such=
 a claim on an unadorned top level package
> +  * `python3-foo-cli` or `python3-foo-bin` - not as nicely discoverable,=
 but `command-not-found` can help, and dh_python3 will work

if someone creates python3-foo-cli binary just to ship /usr/bin/foo it
might as well be foo (if there are no /usr/bin/foo name collisions,
binary package name should be safe as well) so I'd remove it
--=20
Piotr O=C5=BCarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

--mSxgbZZZvrAyzONB
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWFY/kAAoJEK728aKnRXZFXlkP/23/1qi8Bai/GRJ1foclcuS7
Unl3rQJ7NOCot5bxyzL+k8yvOT9NGyyn7hExnerXK3BXU9nwLjx5hDWNoSRf+kE7
53O5f5MSk39cEu5kglZ0Tlhy02ALVa67lzdJkEuiZSIyieca0y3+TAUdveOwMLfg
5+iHdEmVKebCCU45AXf5qHsWP817MFqd17siew7MYexok5rf1rcEQFj82nScRkOs
YzFwR/l5qZptoHPuqpHojp6Z5S0F3TILmzAppqzEACggWAAMgiCiF4N/oK5Ii7Xr
/7voqlFKM4ZMrFkeQ6mMr7jgO68B+PLem7YCSEuB8vbx7cU9uBr8AkR1MpQGpLx5
xeYxVPsOKpp7KHtR1ltrVT4Nd3Ya91/heIJLlPbrYiym7l3uzIMdjeigUqrqtHTv
fwM96Yb2nDLh3XH5KlVjUwjW/I1pHIw27rKtbHHWxXLDFV9rnHwKqkE4KMNGhkhm
egEpn2nore0Dt5H1OZ1ByeuOJ0sLTzx8vxaY/Od686X90Hl1Bzes0Npced+OCIOD
oPwKnIRpbf5DjMUPqECd1t4D0GVNLXnpoAP882/sEx0QmiV4lF0ac1atsTdYcAb7
fT5wkdrBhRrnz+igVGSbBFTMFuum3mn10ZgKPRqJUW+9Iqc/K6SMtoYea3xhY3Q6
2RiYdL61MbvrQZYX7HcC
=xDeA
-----END PGP SIGNATURE-----

--mSxgbZZZvrAyzONB--