I’m a Java developer who’s toyed around with Python on and off. I recently stumbled upon this article which mentions common mistakes Java programmers make when they pick up Python. The first one caught my eye:
A static method in Java does not translate to a Python classmethod. Oh sure, it results in more or less the same effect, but the goal of a classmethod is actually to do something that’s usually not even possible in Java (like inheriting a non-default constructor). The idiomatic translation of a Java static method is usually a module-level function, not a classmethod or staticmethod. (And static final fields should translate to module-level constants.)
This isn’t much of a performance issue, but a Python programmer who has to work with Java-idiom code like this will be rather irritated by typing Foo.Foo.someMethod when it should just be Foo.someFunction. But do note that calling a classmethod involves an additional memory allocation that calling a staticmethod or function does not.
Oh, and all those Foo.Bar.Baz attribute chains don’t come for free, either. In Java, those dotted names are looked up by the compiler, so at runtime it really doesn’t matter how many of them you have. In Python, the lookups occur at runtime, so each dot counts. (Remember that in Python, “Flat is better than nested”, although it’s more related to “Readability counts” and “Simple is better than complex,” than to being about performance.)
I found this a bit strange because the documentation for staticmethod says:
Static methods in Python are similar to those found in Java or C++. Also see classmethod() for a variant that is useful for creating alternate class constructors.
Even more puzzling is that this code:
class A:
def foo(x):
print(x)
A.foo(5)
Fails as expected in Python 2.7.3 but works fine in 3.2.3 (although you can’t call the method on an instance of A, only on the class.)
So there’s three ways to implement static methods (four if you count using classmethod), each with subtle differences, one of them seemingly undocumented. This seems at odds with Python’s mantra of There should be one– and preferably only one –obvious way to do it. Which idiom is the most Pythonic? What are the pros and cons of each?
Here’s what I understand so far:
Module function:
- Avoids the Foo.Foo.f() problem
- Pollutes the module’s namespace more than the alternatives
- No inheritance
staticmethod:
- Keeps functions related to the class inside the class and out of the module namespace.
- Allows calling the function on instances of the class.
- Subclasses can override the method.
classmethod:
- Identical to staticmethod, but also passes the class as the first argument.
Regular method (Python 3 only):
- Identical to staticmethod, but can’t call the method on instances of the class.
Am I overthinking this? Is this a non-issue? Please help!
The most straightforward way to think about it is to think in terms of what type of object the method needs in order to do its work. If your method needs access to an instance, make it a regular method. If it needs access to the class, make it a classmethod. If it doesn’t need access to the class or the instance, make it a function. There is rarely a need to make something a staticmethod, but if you find you want a function to be “grouped” with a class (e.g., so it can be overridden) even though it doesn’t need access to the class, I guess you could make it a staticmethod.
I would add that putting functions at the module level doesn’t “pollute” the namespace. If the functions are meant to be used, they’re not polluting the namespace, they’re using it just as it should be used. Functions are legitimate objects in a module, just like classes or anything else. There’s no reason to hide a function in a class if it doesn’t have any reason to be there.