On Sat, 29 Sep 2018 at 00:21, Martin Dobias <wonder...@gmail.com> wrote:
> > I think for the time being we should still treat the 3D library as > having unstable API - so I wanted to check how others would feel about > having Python API for qgis_3d that would be marked as unstable, i.e. > there may be changes between 3.x releases? I think with big warnings > in the docs that the API may change we can get others to experiment > with 3D functionality while not offending anyone too much if we break > it later. The idea is that the API would get frozen at some point > later in 3.x release cycle or for QGIS 4. I don't see an issue with this -- there's other parts of code exposed to PyQGIS which is also clearly marked as non-stable. Some processing classes for instance. Nyall _______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
