QGIS/python/server/auto_additions/qgsserverparameters.py

# The following has been generated automatically from src/server/qgsserverparameters.h
QgsServerParameter.Name.baseClass = QgsServerParameter
QgsServerParameterDefinition.raiseError = staticmethod(QgsServerParameterDefinition.raiseError)
QgsServerParameter.name = staticmethod(QgsServerParameter.name)
Update sip 2018-06-28 13:32:10 +01:00			`# The following has been generated automatically from src/server/qgsserverparameters.h`
Update sip binding 2018-07-02 08:27:20 +01:00			`QgsServerParameter.Name.baseClass = QgsServerParameter`
[pyqgis] Wrap unambiguously static methods in staticmethod sip doesn't use the standard Python staticmethod type for defining static methods, which means that standard means of testing for a static method (like `isinstance(..., staticmethod)`) fail with any PyQGIS static methods. This causes issues with lint tools, which incorrectly flag calls to QGIS static methods as missing self arguments. It also breaks detection of static methods in the sphinx PyQGIS docs, so all static methods are shown as non-static. Work around this in sipify, by wrapping unambiguously static methods in staticmethod wrappers. 2024-08-14 15:28:33 +10:00			`QgsServerParameterDefinition.raiseError = staticmethod(QgsServerParameterDefinition.raiseError)`
			`QgsServerParameter.name = staticmethod(QgsServerParameter.name)`