Re: Updating python-build/getting rid of pep517
Le 02/08/2023 à 00:09, Scott Kitterman a écrit : * pdm (update to new version, needs pyproject-hooks) [pdm-pep517 can probably go away too] pdm-pep517 was renamed to pdm-backend, which will still be needed by Python packages who want to use it as a build backend. (It does not depend on pyproject-hooks.) Cheers
Re: Updating python-build/getting rid of pep517
On Wed, 2 Aug 2023, Scott Kitterman wrote: On Tuesday, August 1, 2023 7:36:38 PM EDT Scott Talbert wrote: On Tue, 1 Aug 2023, Scott Kitterman wrote: On Tue, 1 Aug 2023, Scott Kitterman wrote: The pep517 package has been renamed pyproject-hooks upstream: https://github.com/pypa/pyproject-hooks It looks like we need this to update python-build to the latest version (which we should definitely do sooner rather than later). Is anyone up for packaging this? Once it's in the archive we ought to make sure all current users of pep517 are switched so we can remove it this cycle. I'll go ahead and start packaging it. Excellent. PEP517 has a few users that will need to be ported/updated: Initial packaging done, on its way into NEW. And it's in Unstable now, so it would be good if people could start updating the relevant team packages. I filed #1042869 for the one package not in DPT. * python-build (update to new version, needs pyproject-hooks) I took care of python-build already as a team upload. Scott T.
Re: Updating python-build/getting rid of pep517
On August 2, 2023 1:34:32 PM UTC, Scott Talbert wrote: >On Wed, 2 Aug 2023, Scott Kitterman wrote: > >> On Tuesday, August 1, 2023 7:36:38 PM EDT Scott Talbert wrote: >>> On Tue, 1 Aug 2023, Scott Kitterman wrote: > On Tue, 1 Aug 2023, Scott Kitterman wrote: >> The pep517 package has been renamed pyproject-hooks upstream: >> >> https://github.com/pypa/pyproject-hooks >> >> It looks like we need this to update python-build to the latest version >> (which we should definitely do sooner rather than later). >> >> Is anyone up for packaging this? >> >> Once it's in the archive we ought to make sure all current users of >> pep517 >> are switched so we can remove it this cycle. > > I'll go ahead and start packaging it. Excellent. PEP517 has a few users that will need to be ported/updated: >>> Initial packaging done, on its way into NEW. >>> >> And it's in Unstable now, so it would be good if people could start updating >> the relevant team packages. I filed #1042869 for the one package not in DPT. >> >> * python-build (update to new version, needs pyproject-hooks) > >I took care of python-build already as a team upload. > >Scott T. Thanks. I just did check-manifest. Scott K
Re: Updating python-build/getting rid of pep517
On August 2, 2023 1:23:15 PM UTC, "Éric Araujo" wrote: >Le 02/08/2023 à 00:09, Scott Kitterman a écrit : >> * pdm (update to new version, needs pyproject-hooks) >>[pdm-pep517 can probably go away too] > >pdm-pep517 was renamed to pdm-backend, which will still be needed by Python >packages who want to use it as a build backend. (It does not depend on >pyproject-hooks.) > Thanks, Is there anything blocking updating pdm? Scott K
pybuild now supports meson
FYI: 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. It should detect meson from the presence of a meson.build file. And it'll re-execute dh's meson driver for the build step for each Python version. Hopefully that helps... (and doesn't cause unexpected FTBFSs) Stefano CCed teams of maintainers of packages matching: grep-dctrl -F Build-Depends,Build-Depends-Arch,Build-Depends-Indep \ -s Package,Build-Depends,Build-Depends-Arch,Build-Depends-Indep \ -e '(\s|^)meson(\s|$)' | \ grep-dctrl -F Build-Depends,Build-Depends-Arch,Build-Depends-Indep \ -s Package \ -e '(\s|^)python3(-all)?(-dev)?(\s|$)' Debian GNOME Maintainers gedit gi-docgen gnome-music gtk-doc libgom libpeas rhythmbox totem Debian Input Method Team keyman Debian Python Team gtg meson-python Eberhard Beilharz keyman (U) Emilio Pozuelo Monfort gtk-doc (U) libpeas (U) rhythmbox (U) FingerForce Team libfprint Francois Mazen gtg (U) Iain Lane gnome-music (U) gtk-doc (U) libpeas (U) Jeremy Bicha gtk-doc (U) libgom (U) Jeremy Bicha gedit (U) gnome-music (U) rhythmbox (U) totem (U) Jeremy Bícha libpeas (U) Jordi Mallach rhythmbox (U) Keyman team keyman (U) Laurent Bigonville gedit (U) gnome-music (U) libgom (U) libpeas (U) rhythmbox (U) totem (U) Maintainers of GStreamer packages gst-python1.0 Marco Trevisan libfprint (U) Michael Biebl gtk-doc (U) libgom (U) libpeas (U) rhythmbox (U) totem (U) Sebastian Dröge gst-python1.0 (U) pitivi Simon McVittie gi-docgen (U) meson-python (U) xdg-desktop-portal (U) Sjoerd Simons libpeas (U) Tim Lunn gnome-music (U) gtk-doc (U) Ulises Vitulli libfprint (U) Utopia Maintenance Team xdg-desktop-portal -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: pybuild now supports meson
On Wed, 02 Aug 2023 at 17:44:24 +, 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. One that I was surprised not to see on the list is dbus-python, which currently uses Meson directly. I'd vaguely planned to try building it using pybuild and meson-python, but pybuild invoking Meson directly might be better. (meson-python itself is a false positive: it's already using pybuild.) smcv
Re: pybuild now supports meson
Hi Simon (2023.08.02_18:23:31_+) > On Wed, 02 Aug 2023 at 17:44:24 +, 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. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: pybuild now supports meson
Stefano Rivera writes: > Hi Simon (2023.08.02_18:23:31_+) >> On Wed, 02 Aug 2023 at 17:44:24 +, 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
Re: Updating python-build/getting rid of pep517
On 2023-08-02 09 h 23, Éric Araujo wrote: Le 02/08/2023 à 00:09, Scott Kitterman a écrit : * pdm (update to new version, needs pyproject-hooks) [pdm-pep517 can probably go away too] pdm-pep517 was renamed to pdm-backend, which will still be needed by Python packages who want to use it as a build backend. (It does not depend on pyproject-hooks.) Cheers I see pdm-pep517 is still a complete package (as opposed to being a virtual package redirecting to pdm-backend). What's the plan for this? I'm asking, since at the moment in Lintian, when we find a `build-backend = "pdm.pep517.api"` line in pyproject.toml, we are recommending people build-depend on python3-pdm-pep517. Should I change something? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
