as I understand it, it's hard, if not impossible, to build pyside6 bindings in a way that an end-user can use a different version of pyside6 at runtime. This is easy in pyqt6 (i can just build against the lowest version of pyqt6 we support and the user can install anything with abi compatibility). For now, pyside6 must run at runtime with the same version I build against. which is unfortunate/inflexible... but possibly unavoidable. (other major projects seem to do it this way too)
as I understand it, it's hard, if not impossible, to build pyside6 bindings in a way that an end-user can use a different version of pyside6 at runtime. This is easy in pyqt6 (i can just build against the lowest version of pyqt6 we support and the user can install anything with abi compatibility). For now, pyside6 must run at runtime with the same version I build against. which is unfortunate/inflexible... but possibly unavoidable. (other major projects seem to do it this way too)