Bug 2255537

Summary:	Review Request: python3-pyside6 - Python bindings for Qt 6
Product:	[Fedora] Fedora	Reporter:	Alex Pyrgiotis <alex.p>
Component:	Package Review	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	farchord, laurent.rineau__fedora, ngompa13, package-review
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-02-24 17:26:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Pyrgiotis 2023-12-21 17:57:50 UTC

Spec URL: https://github.com/apyrgio/python3-pyside6-rpm/blob/main/python3-pyside6.spec
SRPM URL: https://github.com/apyrgio/python3-pyside6-rpm/releases/tag/6.6.1
Description: PySide6 is the official Python module from the Qt for Python project, which provides access to the complete Qt 6.0+ framework.
Fedora Account System Username: -

---

Hi everyone,

This is a draft proposal for a PySide6 package. In this iteration, we actually package the Python wheels for PySide6, which have Qt 6 libraries baked-in. This means that this package is NOT suitable yet for inclusion in the Fedora repos.

Brief backstory, I'm one of the maintainers of Dangerzone [1], and we recently got bit by the fact that python3-pyside2 is no longer maintained [2]. This means that, starting from Fedora 39, we cannot offer Dangerzone to our Fedora and Qubes users.

Since our users add our RPM repo in order to install Dangerzone, we considered offering PySide6 as a separate package. Looking more into this, we realized that this is not a simple task. PySide2/6 depends on private Qt APIs, whose stability is not guaranteed even between patch versions [3]. This means that our PySide6 package would have to be totally in sync with the system Qt 6 package, else we would introduce conflicts during upgrades. This level of synchronization is not feasible for a third-party repo.

So, the next best option is to package the PySide6 Python wheels, which have the Qt 6 libraries baked-in. The linked spec and SRPM files are the result of this work. This approach has several drawbacks (increased package size, no reusability, prebuilt libraries), but it's probably the simplest way forward for a third-party project like ours.

A better approach would be to officially package PySide6, but we would need a sponsor who has some extra familiarity with PySide2/6, to help us with the process. The fact that neither Debian nor Fedora offer PySide6 is probably an indication that this is not a simple task, but we could spend some cycles there. In the meantime, we will roll out our package to our users, meaning that a python3-pyside6 package will be installed in some systems soon. Any pointers on how it's best to roll this out in a forward-compatible way [4] would be very appreciated.

Cheers,
Alex


[1]: https://dangerzone.rocks
[2]: https://pagure.io/fesco/issue/3080
[3]: Similar discussion on the effect of private Qt APIs on Qt5 packages: https://www.spinics.net/lists/fedora-devel/msg303269.html 
[4]: My guess is probably add it at some point in fedora-obsolete-packages, once the official package is out.

Comment 1 Neal Gompa 2024-01-21 18:06:09 UTC

This package is invalid, as it does not build PySide6 from source.

Cf. https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packaged/#prebuilt-binaries-or-libraries

Comment 2 Alex Pyrgiotis 2024-01-23 09:10:54 UTC

Hi Neal,

Thanks for the feedback! Yeap, I'm aware, that's why I mentioned this package is not a candidate for inclusion.
It's actually the package that we will ship to our users via our RPM repo.

What I'm basically saying here though is that we can package PySide6 appropriately, if a Fedora maintainer with PySide/Qt experience can assist us in the process.
If this is not the appropriate place for this question, I can try sending a message to the python-devel list, else wherever you suggest.

Cheers,
Alex

Comment 3 Neal Gompa 2024-01-23 12:22:40 UTC

You may want to reach out to the member of the Fedora KDE SIG working on this too and collaborate: https://pagure.io/fedora-kde/SIG/issue/446

Comment 4 Alex Pyrgiotis 2024-01-29 20:00:01 UTC

Thanks for the heads up Neil, it's great having KDE involved. I'll approach them to see if we can help.

Comment 5 Neal Gompa 2024-02-24 17:26:58 UTC


*** This bug has been marked as a duplicate of bug 2265554 ***