python-devel July 2025

python-devel@lists.fedoraproject.org

6 participants
4 discussions

RFC: retiring python-django4.2 from Rawhide
by Michel Lind 11 Jul '25

11 Jul '25

Dear all, Unless someone objects, I plan to retire python-django4.2 from Rawhide next week. Tests currently fail: https://bugzilla.redhat.com/show_bug.cgi?id=2374048 and Django upstream don't plan to support Python 3.14 on versions older than 5.2 (the current LTS) https://code.djangoproject.com/ticket/35844 Building Django 4.2 without tests just hide the issue, as they will cause downstream builds to fail; these packages will need to be patched to work with Django 5.2 if they have not. Django 4.2 itself is otherwise still supported until 2026, so I don't plan to retire it from any other branch. Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://michel-slm.name/

1 0

Using pyproject macros when setup.py isn't in root directory
by Scott Talbert 10 Jul '25

10 Jul '25

Is there any way to use the pyproject macros when setup.py isn't in the root directory? I maintain a couple of packages where this is the case - one where there are actually two PyPI packages built from the same source package, and another where the Python package is in a subdirectory because it's bindings for a C library that is also built. When I try, I get this error during build: + echo 'ERROR: Neither pyproject.toml nor setup.py found, consider using %pyproject_buildrequires -N <requirements-file> if this is not a Python package.' ERROR: Neither pyproject.toml nor setup.py found, consider using %pyproject_buildrequires -N <requirements-file> if this is not a Python package. There aren't requirements files in the upstream packages. But I guess I could make a downstream one? Thanks, Scott

3 5

PSA: Using %pyproject_wheel and/or %pyproject_install without %pyproject_buildrequires is not supported
by Miro Hrončok 09 Jul '25

09 Jul '25

Hello Python packagers, as many are currently migrating from the old Python RPM macros to the new due to https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros I'd like to reiterate: %generate_buildrequires %pyproject_buildrequires [options...] This is MANDATORY when you use %pyproject_wheel and/or %pyproject_install. The %pyproject_wheel and %pyproject_install macros have dependencies that are generated by %pyproject_buildrequires. Currently, that is python3-pip, python3-packaging and pyproject-rpm-macros. But the list is not stable and may change at any point. For example, if we stop using python3-pip to build the wheel and start using python3-build instead, packages without %pyproject_buildrequires would break. (pyproject-rpm-macros do not Require those packages as the macros are usable with arbitrary Python versions.) Packages without %pyproject_buildrequires and without a manual BuildRequires on pyproject-rpm-macros do not build on RHEL/EPEL. Packages without %pyproject_buildrequires and without a manual BuildRequires on python3-packaging are relying on an indirect transitive dependency from python3-rpm-geneartors. Please, always add the %generate_buildrequires section when converting packages to pyproject macros. =========================================================================== If you cannot use %pyproject_buildrequires, let's talk about a solution to this. Perhaps we could produce a pyproject-rpm-macros-static-buildrequires metapackage with the curated set of Requires? But if you really need this, please tell me your reasons. =========================================================================== Maintainers by package: boom-boot bgurney bmr mcsontos congruity adamwill swt2c cvc5 jjames cxxtest mgieseki flatpak-module-tools kalev otaylor yselkowitz grammalecte melmorabity knot jruzicka pwouters lensfun germano grahamwhiteuk nphilipp rdieter trix libcpuid martinkg libmamba orion llama-cpp man2dev trix menulibre lyessaadi onnxruntime aalvarez dherrera python-PyRSS2Gen adamwill python-Pympler limb python-adafruit-platformdetect orphan python-animatplot davidsch python-azure-sdk-tools jcline python-binary-memcached amoralej python-click-spinner thebeanogamer python-collada hobbes1069 python-contextualbandits iztokf python-filecheck rathann python-ipyparallel ellert python-isal ellert python-metakernel ellert python-mimerender adamwill python-psycopg3 anezbeda ndavidov osloup python-pyownet ttorcz python-resultsdb_api adamwill python-scikit-image orion sergiopr python-scikit-uplift iztokf radicale jorti pbiering till rpkg cqi lsedlar onosek torbrowser-launcher limb pjp tortoisehg kiilerix nbecker tpm2-pkcs11 dcavalca jjelen pbrobinson Packages by maintainer: aalvarez onnxruntime adamwill congruity python-PyRSS2Gen python-mimerender python-resultsdb_api amoralej python-binary-memcached anezbeda python-psycopg3 bgurney boom-boot bmr boom-boot cqi rpkg davidsch python-animatplot dcavalca tpm2-pkcs11 dherrera onnxruntime ellert python-ipyparallel python-isal python-metakernel germano lensfun grahamwhiteuk lensfun hobbes1069 python-collada iztokf python-contextualbandits python-scikit-uplift jcline python-azure-sdk-tools jjames cvc5 jjelen tpm2-pkcs11 jorti radicale jruzicka knot kalev flatpak-module-tools kiilerix tortoisehg limb python-Pympler torbrowser-launcher lsedlar rpkg lyessaadi menulibre man2dev llama-cpp martinkg libcpuid mcsontos boom-boot melmorabity grammalecte mgieseki cxxtest nbecker tortoisehg ndavidov python-psycopg3 nphilipp lensfun onosek rpkg orion libmamba python-scikit-image orphan python-adafruit-platformdetect osloup python-psycopg3 otaylor flatpak-module-tools pbiering radicale pbrobinson tpm2-pkcs11 pjp torbrowser-launcher pwouters knot rathann python-filecheck rdieter lensfun sergiopr python-scikit-image swt2c congruity thebeanogamer python-click-spinner till radicale trix lensfun llama-cpp ttorcz python-pyownet yselkowitz flatpak-module-tools Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 0

Neuro SIG Python packaging strategy change
by Ankur Sinha 08 Jul '25

08 Jul '25

Hi all, We, at the Neuro SIG, have been discussing a change in strategy related to packaging Python software. We maintain ~500 packages at the moment, about 300 are Python. It's a lot of work, and we're struggling to keep up. There's still a lot of software out there we'd like to "support" on Fedora too. https://pagure.io/neuro-sig/NeuroFedora/issue/580 Our primary target audience is researchers/scientists. The goal is for them to be able to use software on Fedora easily. What we're no longer sure about is whether providing system packages is the best way to achieve this, given that anecdotal evidence suggests that most people will set up virtual environments etc. and install packages directly from pypi. I am not aware of any users at all that rely on system packages (including me nowadays). So, we're thinking of: - prioritising packaging/maintaining software that is unavailable on PyPi (or difficult to install from there) - dropping software that is pip installable from Fedora - shifting focus to testing that the software we care about is pip installable on current Fedora releases - documenting software status (pip installable or not) and any additional tips/steps required to get it working and informing upstream of issues that we encounter and submitting fixes where possible This is the general plan. Folks are, of course, welcome to maintain packages that they think are useful as system packages, for example tools that provide command line interfaces and so on. If possible, perhaps we can run simple import tests to check that pip installed packages also "function correctly". I don't know how much work it would be to install stuff using pip and figuring out a way to get its code (from the source repo) and running unit tests etc.---but that's something we thought we can look into later if we have the resources. For the simple "check whether X installs on Fedora via pip", I thought perhaps "tmt" could be used, but I haven't looked into it in detail yet. https://docs.fedoraproject.org/en-US/ci/tmt/ What do you all think about this? Please share any thoughts you have about this, and any tips/tricks/tools that can be used. If it's something we can do for Python software in Fedora in general, we'd be happy to do that too. -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London

3 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-devel July 2025