Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump PySide2 to PySide6 #60

Open
microhobby opened this issue May 18, 2023 · 4 comments
Open

Bump PySide2 to PySide6 #60

microhobby opened this issue May 18, 2023 · 4 comments
Assignees
Labels
Torizon 6.x.y Improve support to Torizon 6.x.y

Comments

@microhobby
Copy link
Member

The issue we have today is that apparently we don't have the PySide6 packages for armv7 and armv8.
One possibility would be PyQt6: https://www.pythonguis.com/faq/pyqt6-vs-pyside6/

@microhobby microhobby added the Torizon 6.x.y Improve support to Torizon 6.x.y label May 18, 2023
@escherstair
Copy link
Contributor

Hi @microhobby
I don't know from the technical point of view, but from the licensing point of view, I don't think PyQt6 is an option.
From https://www.pythonguis.com/faq/pyqt6-vs-pyside6/ I see that

Licensing

The main notable difference between the two versions is licensing — with PyQt6 being available under a GPL or commercial license, and PySide6 under a LGPL license.

If you are planning to release your software itself under the GPL, or you are developing software which will not be distributed, the GPL requirement of PyQt6 is unlikely to be an issue. However, if you want to distribute your software but not share your source code you will need to purchase a commercial license from Riverbank for PyQt6 or use PySide6.

and on the FAQ on the implications of GPL vs LGPL licensing in PyQt/PySide apps.

I think that python3Pyside2QML is the only template that uses PySide2 (and maybe will use PyQt6), and so it's the only one impacted by licensing issue.
Can you confirm this?

@microhobby
Copy link
Member Author

hey @escherstair, yes this license subject is also something to think of. As you pointed, I agree that because this license we should not go to PyQt6, since maybe we will have users that should not agree to share their application source code.

The option that left is build the binaries in the Dockerfile. The con is that the maintainer will have more maintenance work, instead of only use the Debian package.

@escherstair
Copy link
Contributor

I imagine you look here for the packages, and both armv7 and armv8 arch are not available.

I'm not an expert, but aren't these packages ok?

@microhobby
Copy link
Member Author

Hey @escherstair,

we need to check from Debian https://packages.debian.org/bookworm/pyside2-tools
So, for pyside we have only the pyside2 on Debian Bookworm.
We check for Debian because the base images used by Toradex, and Toradex provide packages for specific hardware libs, are based on Debian.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Torizon 6.x.y Improve support to Torizon 6.x.y
Projects
None yet
Development

No branches or pull requests

3 participants