QGIS/python/core/auto_additions/qgscredentials.py

# The following has been generated automatically from src/core/qgscredentials.h
try:
    QgsCredentialsNone.__attribute_docs__ = {'destroyed': "signals that object will be destroyed and shouldn't be used anymore\n"}
except NameError:
    pass
try:
    QgsCredentialsConsole.__attribute_docs__ = {'destroyed': "signals that object will be destroyed and shouldn't be used anymore\n"}
except NameError:
    pass
QgsCredentials.instance = staticmethod(QgsCredentials.instance)
Collect attribute docstrings for PyQGIS documentation 2024-08-13 13:47:46 +10:00			`# The following has been generated automatically from src/core/qgscredentials.h`
Be tolerant against optional sip modules 2024-08-14 09:45:06 +10:00			`try:`
			`QgsCredentialsNone.__attribute_docs__ = {'destroyed': "signals that object will be destroyed and shouldn't be used anymore\n"}`
			`except NameError:`
			`pass`
			`try:`
			`QgsCredentialsConsole.__attribute_docs__ = {'destroyed': "signals that object will be destroyed and shouldn't be used anymore\n"}`
			`except NameError:`
			`pass`
[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			`QgsCredentials.instance = staticmethod(QgsCredentials.instance)`