silx icon indicating copy to clipboard operation
silx copied to clipboard
verified publisher icon silx-kit

Changing preferred Qt binding from pyqt5 to qt6

Open t20100 opened this issue 1 year ago • 1 comments

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: https://github.com/silx-kit/silx/blob/a7da2634a2a26e1b77ea3e4bdf080027da2a7c0a/src/silx/gui/qt/_qt.py#L67
  • 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 avatar Aug 30 '24 14:08 t20100

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

mretegan avatar Sep 02 '24 06:09 mretegan

+1 for PyQt6 as well

loichuder avatar Feb 13 '25 13:02 loichuder

@loichuder PyQt6 or PySide or any of those?

t20100 avatar Feb 17 '25 08:02 t20100

I'd like to do this before the "dev week" event and benefit from the event as first testing ;)

t20100 avatar Feb 17 '25 08:02 t20100

@loichuder PyQt6 or PySide or any of those?

No real preference. I used both without issues but this is not really representative.

loichuder avatar Feb 17 '25 09:02 loichuder

PySide6 as default for me (while supporting PyQt6 of course).

PySide6 simplifies deployment of solutions on MacOS because of providing universal wheels. PyQt6 does not do it.

vasole avatar Feb 18 '25 10:02 vasole