Hi Stuart, Thanks for your changes to python-qtpy on salsa - looks great!
What about the transition, though? There are quite a few packages in unstable/testing that currently depend on python3-qtpy and will need to transition to one of the other packages or manually specify the Qt/PySide libraries that they require. Here are some possibilities: (1) Upload the new qtpy, and then file serious bugs against all of these packages, requiring them to update their dependencies immediately. (2) Change python3-qtpy to depend on python3-qtpy-qt5 for the time being, and file important bugs against the depending packages, asking them to switch to one of the python3-qtpy-* packages, and giving a timeline for dropping the -qt5 dependency (presumably early in the next release cycle). (3) File important bugs against the depending packages, asking them to change their dependencies to something like python3-qtpy-qt5 | python3-qtpy (<< 2.4.1-3) (where -qt5 can obviously be replaced with one of the other metapackages), with a deadline, and after that time, doing NMUs where needed and then updating the python3-qtpy package to 2.4.1-3 with these changes. I think (2) is probably the most sensible: it still addresses the requirements of this bug report without instantly breaking a bunch of other packages. (2) combined with the suggestion in (3) for how to change the dependencies is probably what I would go with. The downside of (2), though, is that it still pulls in the whole of -qt5, but since many users will already have that installed, it does not seem like such an issue. Presumably the applications that require PySide 6 or Qt6 will specify this in their calls to pyqt (by setting the appropriate environment variable or something like that). Best wishes, Julian
