Control: found -1 5.6.1-2
Hi!
I don't think an explicit dependency on only Qt5 is the right fix for
python3-qtconsole.
- python3-qtconsole is a widget not an application
- python3-qtconsole doesn't ship any executables of its own
- python3-qtconsole works with QtPy5 QtPy6 and PySide6
The current situation is that a package using python3-qtconsole with
PyQt6 will depend on PyQt6 packages for correct operation, and also
uselessly install PyQt5 packages via python3-qtconsole's dependency on
PyQt5.
My conclusion is that it's not up to python3-qtconsole to have an
opinion on what toolkit the programs using it should require and
therefore python3-qtconsole shouldn't declare a dependency on any
particular Python-Qt implementation. Its dependency on python3-qtpy is
sufficient for python3-qtconsole, and its rdepends take responsibility
for specifying the implementation.
One such rdep is jupyter-qtconsole - as an application, it should
specify which Qt implementation is used.
I'm happy to do a team upload to move the pyqt5 dependencies from
python3-qtconsole to jupyter-qtconsole later in the week.
As a separate item, build-deps and autopkgtest deps on all of the
available Qt implementations for the purposes of testing with each one
might be appropriate. If that is attractive for this package, then there
is suitable code in debian/rules and debian/tests/* in magicgui,
superqt, and qwt that can be adapted.
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
