Hi all,
Am I the only QGIS dev highly frustrated by the bottleneck of sip-build > when building QGIS? Can we do something (funding upstream?) to improve > that? I used to be quite frustrated when sip4 support was dropped, as sip-build times were really terrible with sip 6 at the time. After David's fixes in Oct/Nov 2025 though, things are back to normal. With sip-tools v6.15+ I don't think sip-build is a bottleneck any more for me. I'm more annoyed that touching any enum or docstring in qgis.h will trigger an almost full rebuild of the whole project! Though, I still often do `ninja qgis` during iterative rebuilds to avoid sip-build if not strictly necessary. > - we bind to Python a very large part of our header files (more than > half). I've always found that the amount of things exposed to Python was > excessive. IMHO we should be much more conservative, and wait for plugin > authors to ask for an API to be exposed, rather than expose it prematurely. > My personal preference would be to expose as much as the stable API promise allows us to, then encourage development of new and often niche features to be done as python plugins instead of having them in core. Best, Stefanos
_______________________________________________ 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
