Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From: Nicholas D Steeves <sten@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: pybuild now supports meson
Date: Wed, 02 Aug 2023 22:30:01 +0200
Message-ID: <GYqDL-4FEx-3@gated-at.bofh.it>
References: <GYo8V-4DTE-5@gated-at.bofh.it> <GYoLD-4EnY-3@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Wed Aug  2 20:20:20 2023
Old-Return-Path: <sten@debian.org>
X-Amavis-Spam-Status: No, score=-108.52 tagged_above=-10000 required=5.3 tests=[ATTENDEES_DBSPAM_BODY3=1, BAYES_00=-2, 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, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
MIME-Version: 1.0
Content-Type: text/plain
X-Debian-User: sten
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/21017
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/87cz055h9a.fsf@digitalMercury.freeddns.org
Approved: robomod@news.nic.it
Lines: 24
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Wed, 02 Aug 2023 16:19:45 -0400
X-Original-Message-ID: <87cz055h9a.fsf@digitalMercury.freeddns.org>
X-Original-References: <20230802174424.kblpsp7hac2sqygj@satie.tumbleweed.org.za> <ZMqfIznZ5eBObij2@tautology.pseudorandom.co.uk>
Xref: csiph.com linux.debian.maint.python:15099

Stefano Rivera <stefanor@debian.org> writes:

> Hi Simon (2023.08.02_18:23:31_+0000)
>> On Wed, 02 Aug 2023 at 17:44:24 +0000, Stefano Rivera wrote:
>> > The latest upload of dh-python to unstable (6.20230802) includes a
>> > meson plugin, so pybuild can easily build a package multiple times for
>> > all supported Python modules.
>> 
>> I don't think this is necessarily appropriate for a lot of the packages
>> in the dd-list: many of them don't install any public Python modules,
>> only private Python modules for internal use (often only for their
>> tests). It seems better for those to keep using Meson directly, to match
>> upstream expectations and give their maintainers full control over their
>> build options.
>
> Make sense.

Is there a better method for fuzzing these modules with CI--as an early
warning system for new Python releases?  Would it be useful to activate
the meson dh-python plugin somewhere like reprobuilds, DebCI, or Salsa
CI, while leaving it deactivated on buildds?

Cheers,
Nicholas