[QGIS-Developer] SIP is insane
Raymond Nijssen
r.nijssen at terglobo.nl
Mon Jun 8 06:38:36 PDT 2026
On 6/6/26 02:18, Even Rouault via QGIS-Developer wrote:
> 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.
Not sure which part this would be, but it reminds me of the "old days"
when Python bindings were made by hand and a big part of the API was not
exposed. As a plugin developer I needed to ask core developers to expose
a class or function to Python and wait for it to happen.
Then I needed to build QGIS (which I can) but after finishing the plugin
my customers had to wait for months (if not a years) for the next QGIS
release to be able to run the plugin on their company wide QGIS (LTR)
installation.
Not nice for the core developers (I guess making Python bindings is not
the most fun task), not nice for plugin developers and not nice for QGIS
users in need for a new plugin.
I'm also wondering how many plugins would break if we would suddenly
quit exposing part of the API. Even if we scan the entire plugin
repository, there are many more plugins in the world.
So, I'm really happy with the current approach of exposing everything.
If this can be more efficient somehow that would of course be wonderful.
Kind regards,
Raymond
More information about the QGIS-Developer
mailing list