gotchapythonCritical
What is the difference between @staticmethod and @classmethod in Python?
Viewed 0 times
staticmethodclassmethodthepythondifferenceandbetweenwhat
Problem
What is the difference between a method decorated with
@staticmethod and one decorated with @classmethod?Solution
Maybe a bit of example code will help: Notice the difference in the call signatures of
Below is the usual way an object instance calls a method. The object instance,
With classmethods, the class of the object instance is implicitly passed as the first argument instead of
You can also call
a classmethod, it is probably because you intend to call it from the class rather than from a class instance.
One use people have found for class methods is to create inheritable alternative constructors.
With staticmethods, neither
Staticmethods are used to group functions which have some logical connection with a class to the class.
you get a "partially applied" version of the function with the object instance
With
Here, with a staticmethod, even though it is a method,
a good 'ole function with no arguments bound.
And of course the same thing happens when you call
foo, class_foo and static_foo:class A(object):
def foo(self, x):
print(f"executing foo({self}, {x})")
@classmethod
def class_foo(cls, x):
print(f"executing class_foo({cls}, {x})")
@staticmethod
def static_foo(x):
print(f"executing static_foo({x})")
a = A()Below is the usual way an object instance calls a method. The object instance,
a, is implicitly passed as the first argument.a.foo(1)
# executing foo(, 1)With classmethods, the class of the object instance is implicitly passed as the first argument instead of
self.a.class_foo(1)
# executing class_foo(, 1)You can also call
class_foo using the class. In fact, if you define something to bea classmethod, it is probably because you intend to call it from the class rather than from a class instance.
A.foo(1) would have raised a TypeError, but A.class_foo(1) works just fine:A.class_foo(1)
# executing class_foo(, 1)One use people have found for class methods is to create inheritable alternative constructors.
With staticmethods, neither
self (the object instance) nor cls (the class) is implicitly passed as the first argument. They behave like plain functions except that you can call them from an instance or the class:a.static_foo(1)
# executing static_foo(1)
A.static_foo('hi')
# executing static_foo(hi)Staticmethods are used to group functions which have some logical connection with a class to the class.
foo is just a function, but when you call a.foo you don't just get the function,you get a "partially applied" version of the function with the object instance
a bound as the first argument to the function. foo expects 2 arguments, while a.foo only expects 1 argument.a is bound to foo. That is what is meant by the term "bound" below:print(a.foo)
# >With
a.class_foo, a is not bound to class_foo, rather the class A is bound to class_foo.print(a.class_foo)
# >Here, with a staticmethod, even though it is a method,
a.static_foo just returnsa good 'ole function with no arguments bound.
static_foo expects 1 argument, anda.static_foo expects 1 argument too.print(a.static_foo)
# And of course the same thing happens when you call
static_foo with the class A instead.print(A.static_foo)
# Code Snippets
class A(object):
def foo(self, x):
print(f"executing foo({self}, {x})")
@classmethod
def class_foo(cls, x):
print(f"executing class_foo({cls}, {x})")
@staticmethod
def static_foo(x):
print(f"executing static_foo({x})")
a = A()a.foo(1)
# executing foo(<__main__.A object at 0xb7dbef0c>, 1)a.class_foo(1)
# executing class_foo(<class '__main__.A'>, 1)A.class_foo(1)
# executing class_foo(<class '__main__.A'>, 1)a.static_foo(1)
# executing static_foo(1)
A.static_foo('hi')
# executing static_foo(hi)Context
Stack Overflow Q#136097, score: 4020
Revisions (0)
No revisions yet.