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

Changing preferred Qt binding from pyqt5 to qt6 #4168

Open
t20100 opened this issue Aug 30, 2024 · 1 comment · May be fixed by #4170
Open

Changing preferred Qt binding from pyqt5 to qt6 #4168

t20100 opened this issue Aug 30, 2024 · 1 comment · May be fixed by #4170
Labels
Milestone

Comments

@t20100
Copy link
Member

t20100 commented Aug 30, 2024

Qt5 has reaching the end of regular support mid-2023 and only receives updates under extended commercial support
silx issues occuring with Qt5 but not Qt6 starts to be reported (see #4135).

IMO, it's timely to consider changing the default Qt binding used by silx, this means:

  • Changing the priorities of the different Qt bindings. Current priorities:
    bindings = "PyQt5", "PySide6", "PyQt6"
  • Changing the Qt binding installed with pip install silx[full]

Support of PyQt5 will remain, it will just no longer be selected by default.

The following question is: PySide6 or PyQt6 ?
I'm +1for PySide6.

@t20100 t20100 added this to the Next release milestone Aug 30, 2024
@mretegan
Copy link
Member

mretegan commented Sep 2, 2024

I don't see any downside to changing to PySide6, so +1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants