-
Notifications
You must be signed in to change notification settings - Fork 25
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
Comments
Hi @microhobby
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. |
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. |
Hey @escherstair, we need to check from Debian https://packages.debian.org/bookworm/pyside2-tools |
Hey, I am facing the same issue. How can I use pyside2 on bookworm? I can't manage to make it work with the packages available. Appreciate any help! |
This should be the status of pyside6 in Debian. |
The issue we have today is that apparently we don't have the PySide6 packages for
armv7
andarmv8
.One possibility would be PyQt6: https://www.pythonguis.com/faq/pyqt6-vs-pyside6/
The text was updated successfully, but these errors were encountered: