A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-September/091548.html below:

[Python-Dev] why different between staticmethod and classmethod on non-callable object?

[Python-Dev] why different between staticmethod and classmethod on non-callable object? [Python-Dev] why different between staticmethod and classmethod on non-callable object?Terry Reedy tjreedy at udel.edu
Wed Sep 2 02:50:37 CEST 2009
Greg Ewing wrote:
> Benjamin Peterson wrote:
> 
>> It depends on whether you're keeping the "callable" object around or
>> not. Somebody could add a __call__ method later.
> 
> Good point. Removing the check sounds like the
> right thing to do, then.

Both classmethod & staticmethod are documented as having a *function* 
(callable, as I interprete that) as their single argument. Seems 
reasonable to me. Turning the argument into a function after the fact 
seems like a really esoteric use case.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4