I see that this project recently added an explicit dependency on PyQt5, while also relying on qtpy. Is there a reason to bypass the qtpy wrappers? They should be compatible and, if we stick to qtpy, PySide2 compatibility is given for free.
But maybe I am missing a technical detail.
(This is important for the conda-forge packaging aspects, where we prefer to remain binding-agnostic so people can choose pyqt or pyside, plugins included).
Hi team!
I see that this project recently added an explicit dependency on PyQt5, while also relying on
qtpy
. Is there a reason to bypass theqtpy
wrappers? They should be compatible and, if we stick toqtpy
, PySide2 compatibility is given for free.But maybe I am missing a technical detail.
(This is important for the conda-forge packaging aspects, where we prefer to remain binding-agnostic so people can choose pyqt or pyside, plugins included).