On 10/29/26 12:46, Michael J Gruber wrote:
Hi there,
while it's fall in some parts of the northern hemisphere and autumn in
others, some thoughts on leaf packages, especially in language
ecosystems.
Those thoughts are triggered by upstream changes in a python package
that I maintain. I spent quite some time keeping it building in
Fedora, and now trying things to follow the upstream changes according
to our packaging principles, but I'm finally wondering:
What for?
If it was possible to pip install and try to resolve from dnf first
before going to PyPI, it might not be as problematic. On the developer's
side it gets quite frustrating when you have a dependency that is
compiled and there is not a compatible version in PyPI so the package
needs to be built from source, and then you hit issues of not having
compilers, etc. Every year I get this issue with pydantic-core. And
heads up ruamel.yaml.clib will not have python3.15+ versions at all.
Another aspect is the python-sig's very early rebuilds and
incompatibility detection. I find that many of those bugs are filed by
someone in our sphere, especially when upstream can't do early tests
themselves because of :point_up:.
I do agree that many packages would generally need little actual work,
but maybe the workflow can be made smoother?
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
