Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15099
| From | Nicholas D Steeves <sten@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: pybuild now supports meson |
| Date | 2023-08-02 22:30 +0200 |
| Message-ID | <GYqDL-4FEx-3@gated-at.bofh.it> (permalink) |
| References | <GYo8V-4DTE-5@gated-at.bofh.it> <GYoLD-4EnY-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
pybuild now supports meson Stefano Rivera <stefanor@debian.org> - 2023-08-02 19:50 +0200
Re: pybuild now supports meson Simon McVittie <smcv@debian.org> - 2023-08-02 20:30 +0200
Re: pybuild now supports meson Stefano Rivera <stefanor@debian.org> - 2023-08-02 21:20 +0200
Re: pybuild now supports meson Nicholas D Steeves <sten@debian.org> - 2023-08-02 22:30 +0200
csiph-web