QGIS/python/core/auto_additions/qgslogger.py

# The following has been generated automatically from src/core/qgslogger.h
try:
    QgsLogger.warning = staticmethod(QgsLogger.warning)
    QgsLogger.critical = staticmethod(QgsLogger.critical)
    QgsLogger.fatal = staticmethod(QgsLogger.fatal)
    QgsLogger.debugLevel = staticmethod(QgsLogger.debugLevel)
    QgsLogger.logMessageToFile = staticmethod(QgsLogger.logMessageToFile)
    QgsLogger.logFile = staticmethod(QgsLogger.logFile)
except (NameError, AttributeError):
    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			`# The following has been generated automatically from src/core/qgslogger.h`
[sipify] Minor cleanup to auto additions Condense injections into a single block instead of multiple separate blocks 2024-09-09 09:54:21 +10:00			`try:`
			`QgsLogger.warning = staticmethod(QgsLogger.warning)`
			`QgsLogger.critical = staticmethod(QgsLogger.critical)`
			`QgsLogger.fatal = staticmethod(QgsLogger.fatal)`
			`QgsLogger.debugLevel = staticmethod(QgsLogger.debugLevel)`
			`QgsLogger.logMessageToFile = staticmethod(QgsLogger.logMessageToFile)`
			`QgsLogger.logFile = staticmethod(QgsLogger.logFile)`
auto sipify 🍺 2024-12-03 07:47:10 +00:00			`except (NameError, AttributeError):`
[sipify] Minor cleanup to auto additions Condense injections into a single block instead of multiple separate blocks 2024-09-09 09:54:21 +10:00			`pass`