Hi all,
Regarding switching to "Qt for Python", I made a report on where I was last time I worked on a possible transition to Qt for Python (december 2023) [0] My feelings: - While trying to transition from SIP to QtForPython, I met so many surprises/special-cases/SIP-specific-behaviors that I think we are now very tightly bounded to it - It's very difficult to predict the needed time required to make the whole transition, you have no idea how many surprises you gonna met - Even if I enjoyed many things from QtForPython, we have no garantee that it would be better in the end We could try to lessen adherence to SIP to ease a possible future transition (replace SIP_FACTORY/SIP_TRANSFER with unique_ptr for instance). > Do we have any advantage migrating to PySide (now it is called the official > Qt for Python)? > If yes I am more than willing to adjust my plug-ins. Normally, no adjustement (or very few) would be needed (for thoses importing from qgis.PyQt at least) Regards, Julien [0] https://github.com/qgis/QGIS-Enhancement-Proposals/issues/237#issuecomment-1839008093 > Hi all, > > Just want to remind you about the QEP about switching to PySide (Qt > for Python) [0]. > But I have no idea if such a move will solve issues raised here. > > [0] https://github.com/qgis/QGIS-Enhancement-Proposals/issues/237 -- Julien Cabieces Senior Developer at Oslandia [email protected] _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
