Think the quote is premature optimization is the root of all evil. Don’t know who came up with that famous expression.

In the case of the code in the process guard, perhaps you are right.

In the case of embedding a class within FoldableDockWidget, it’s simply a case of don’t do that, not optimization.

Hardwiring a particular implementation of the Windowing python wrapper is necessary.

qasync

Python library for using asyncio in Qt-based applications

^^ is the package to support them all.

This comes directly from an app i wrote,

from qasync import (asyncSlot, QtWidgets, QtGui, QtCore, _make_signaller)

Here is some code which deals with differences between implementations

from qasync import (QtWidgets, QtCore, QtGui, QtModuleName)

__all__ = ["QtportQAction", "QtportQScreen", "QtportQScreenImplementation"]

try:
    QtportQAction = QtWidgets.QAction
except AttributeError as e:
    #"PySide6", "PyQt6"
    QtportQAction = QtGui.QAction

try:
    QtportQScreen = QtWidgets.QDesktopWidget
    QtportQScreenImplementation = "QDesktopWidget"
except AttributeError as e:
    QtportQScreen = QtGui.QScreen
    QtportQScreenImplementation = "QScreen"

So it can be done!

In the case of this gist, it’s premature optimization. Generally it’s necessary cuz new implementations come along often.