python-devel April 2026

python-devel@lists.fedoraproject.org

6 participants
5 discussions

Announcing pyproject-rpm-macros (1.21.0)
by Tomas Hrnciar 30 Apr '26

30 Apr '26

Hello, I'd like to announce a new version of pyproject-rpm-macros (1.21.0). From now on, the extras passed into %pyproject_buildrequires -x are validated against the project's metadata. The build will now fail in Fedora >=45 and RHEL >=11 if a specified extra does not exist. On older releases, it will emit a warning. There are about 30 packages affected by this change. I've opened PRs with a fix for all of them, and several of these have already been merged. I've BCCed all remaining maintainers whose packages still require updates. Have a nice day, thrnciar

1 0

%pyproject_patch_dependency macro now available (provisional)
by Charalampos Stratakis 24 Apr '26

24 Apr '26

Hello folks, Tired of figuring out the right sed or patch to modify dependency constraints in your Python packages? Or having your carefully crafted regex break because upstream reformatted their metadata? %pyproject_patch_dependency is here to help. A new macro has been merged into pyproject-rpm-macros and is available in Rawhide, F44 and F43 as a provisional feature. It provides a uniform way to override upstream dependency constraints in %prep, regardless of the build backend. It affects both BuildRequires and runtime Requires. Example usage: %prep %autosetup -p1 %pyproject_patch_dependency cython:drop_upper %pyproject_patch_dependency numpy:set_upper:3.0 %pyproject_patch_dependency legacy-dep:ignore It also handles circular/sibling dependencies in multi-wheel specs via the br_only suffix. A sibling package can be ignored in BuildRequires (since it's not yet installed during build) while keeping it as a runtime Requires: %pyproject_patch_dependency sibling-package:ignore:br_only The feature is marked provisional, meaning the API may change based on real-world usage. If you maintain Python packages and deal with dependency version overrides, I'd appreciate if you gave this a try and reported any issues. Documentation (Provisional: Overriding dependency constraints section) <https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/READ…> <https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/READ…> Implementation <https://src.fedoraproject.org/rpms/pyproject-rpm-macros/c/5d9798f289ea8cbeb…> F44 bodhi update <https://bodhi.fedoraproject.org/updates/FEDORA-2026-c50219cb79> F43 bodhi update <https://bodhi.fedoraproject.org/updates/FEDORA-2026-051d1b3285> -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat

1 0

Long option support for pyproject RPM macros?
by Miro Hrončok 21 Apr '26

21 Apr '26

Hey Pythonistas, For a long time, I was considering whether we could have long options for pyproject RPM macros. E.g. %pyproject_save_files --assert-license I drafted something today using LLM and would like to know your opinions: https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/574 Obviously, having long options support is a benefit for readability of the spec files. However, is it worh it? All the argument processing now lives in a custom Lua code. Would you use this? -- Miro Hrončok -- Phone: +420777974800

3 2

Migrating package to meson - what to do about dist-info
by Alexander Ploumistos 12 Apr '26

12 Apr '26

Hello, Bubblemail is about to switch to the meson build system and I have been trying to adapt the package. It feels like it's being held together with scotch tape, but the attached spec file works. One thing I noticed and then I found the note in the Python packaging guidelines, is that the dist-info directory is no longer included in the package. Also, since I've had to drop several python macros, the content of that directory is not the same as before. Since I MUST include the metadata, I would like some help regarding the proper way to do this. I also have a strong suspicion that other things might be amiss in the spec file. The Meson code changes haven't been merged yet into the master branch, they are here: https://framagit.org/razer/bubblemail/-/tree/meson?ref_type=heads Best regards, A.

2 3

pyproject-rpm-macros 1.19.0: A new directory option for %pyproject_buildrequires and %pyproject_wheel
by Miro Hrončok 08 Apr '26

08 Apr '26

Hello Pythonistas, pyproject-rpm-macros 1.19.0 was just built and it provides a small enhancement. Consider this code: %generate_buildrequires pushd nemo-audio-tab >&2 %pyproject_buildrequires popd >&2 pushd nemo-pastebin >&2 %pyproject_buildrequires popd >&2 It can now be replaced with: %generate_buildrequires %pyproject_buildrequires -d nemo-audio-tab %pyproject_buildrequires -d nemo-pastebin Same for %pyproject_wheel. See the documentation in README, section *Building wheels from custom directories* https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/READ… Beware: As this is a new option for the macros, if your spec file uses it, you cannot parse it with an old version of the macros installed. This includes running commands like fedpkg prep, fedpkg srpm etc. Updates are available in Bodhi for all Fedora releases and I plan to update the package in c9s and c10s during the current RHEL development cycle. Happy packaging. -- Miro Hrončok -- Phone: +420777974800

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-devel April 2026