Terry Reedy tjreedy at udel.edu
Wed Sep 2 02:50:37 CEST 2009

• Previous message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
• Next message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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.

---

• Previous message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
• Next message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list