@staticmethod stacked with a custom decorator

Question

Accepted Answer

Decorator order here is critical. @staticmethod must be the outermost decorator - the one applied last - because staticmethod is a descriptor that tells Python's attribute lookup not to inject 'self' or 'cls'. If you write @staticmethod on top of @log_call, Python applies log_call first (wrapping the function), then wraps that result in staticmethod. That's correct. If you accidentally flip the order - @log_call on top of @staticmethod - then log_call receives a staticmethod object, not a callable function. Calling func(*args, **kwargs) inside the wrapper tries to call the descriptor object, not the underlying function, which raises TypeError. The same issue applies to @classmethod. The rule: @staticmethod and @classmethod must always be the outermost decorators. Any custom decorator placed above them will receive a descriptor object, not a plain function, and will break in subtle ways that only surface at call time.