Groups > linux.debian.maint.python > #14066

rstcheck: how should I package the new public module?

Path	csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod
From	Timo Röhling <roehling@debian.org>
Newsgroups	linux.debian.maint.python
Subject	rstcheck: how should I package the new public module?
Date	Mon, 18 Apr 2022 19:30:01 +0200
Message-ID	<EdDmh-9BA2-3@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Apr 18 17:22:21 2022
Old-Return-Path	<roehling@debian.org>
X-Amavis-Spam-Status	No, score=-113.01 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DKIM_WELCOMELIST=0.001, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
X-Greylist	delayed 382 seconds by postgrey-1.36 at bendel; Mon, 18 Apr 2022 17:22:11 UTC
Mail-Followup-To	debian-python@lists.debian.org
Organization	The Debian Project
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="goobnuaion3e76km"
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/19890
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20220418171546.ma2uotpb453aygnt@mail.gaussglocke.de
Approved	robomod@news.nic.it
Lines	69
Sender	robomod@news.nic.it
X-Original-Date	Mon, 18 Apr 2022 19:15:46 +0200
X-Original-Message-ID	<20220418171546.ma2uotpb453aygnt@mail.gaussglocke.de>
Xref	csiph.com linux.debian.maint.python:14066

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

rstcheck used to be a pure CLI application, so I packaged it as
"rstcheck" with a private module in /usr/share/rstcheck. The latest
version has added a public module interface, so "import rstcheck"
has become a thing and the module needs to be installed publicly for
that.

My question is: should I move/rename the whole package to
python3-rstcheck (and keep rstcheck temporarily as transitional
dummy package), or should I keep /usr/bin/rstcheck in the old
package indefinitely and only move the module to python3-rstcheck?

The latter solution feels cleaner to me, because it neatly separates
the library and the appliation, but at the cost of an almost empty
binary package, which is frowned upon by the FTP team. Any
suggestions how I should proceed?


Cheers
Timo

-- 
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

rstcheck: how should I package the new public module? Timo Röhling <roehling@debian.org> - 2022-04-18 19:30 +0200
  Re: rstcheck: how should I package the new public module? Julian Gilbey <julian@d-and-j.net> - 2022-04-18 20:30 +0200

csiph-web