It used to matter more back in Python 2, where the instance-ness of instance methods was enforced more strongly:
>>> class B:
... def f(x):
... print("x is", x)
...
>>> B.f(1)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: unbound method f() must be called with B instance as first argument (
got int instance instead)
You had to mark static methods with @staticmethod back then.
These days, @staticmethod still makes it clearer that the method is static, which helps with code readability and documentation generation, and it lets you call the method on instances without the system trying to bind self.
staticmethodprovides very little utility. The thing it does is let you do is call it from an instance of the class as well as from the class. So try doingB().f(1)andA().f(1). I'm pretty sure it's only there for people coming from languages like Java that force you to write class definitions for everything. I would pretty much always just use a stand-alone function instead of a staticmethod - juanpa.arrivillaga