[issue32070] Clarify the behavior of the staticmethod builtin

[Andrés Delfino]

Andrés Delfino  added the comment:

Also see #34085 that deals with the same issue in functions.rst.

--
nosy: +adelfino

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32070] Clarify the behavior of the staticmethod builtin

[Raymond Hettinger]

Change by Raymond Hettinger :


--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32070] Clarify the behavior of the staticmethod builtin

[Raymond Hettinger]

Raymond Hettinger  added the comment:

ISTM the current wording is correct and aims to describe how staticmethods 
differ from regular methods.   With a regular methods we have "c.m(*a) -> 
type(c).m(c, *a)" and "C.m(*a) -> C.m(*s)".  With a class method, only the 
first of those changes to "c.m(*a) -> type(c).m(*a)". Expressed in English, 
this change is "the instance is ignored except for its class...".

That said, the staticmethod() docs could use a complete rewrite.  They amble 
all over the place and don't directly speak to what a static method is for 
(attaching regular functions to classes to improve findability) or how they 
work (use descriptor logic to suppress the usual behavior of prepend "self" to 
the argument list when called from an instance) or a concise motivating example.

--
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32070] Clarify the behavior of the staticmethod builtin

[Jesse SHapiro]

New submission from Jesse SHapiro :

It looks like the original staticmethod docstring might have been based on the 
classmethod docstring, and it seems like the current description might not be 
accurate.

Current string:

...It can be called either on the class (e.g. C.f()) or on an instance (e.g. 
C().f()); the instance is ignored except for its class...

Proposed change:

It can be called either on the class (e.g. C.f()) or on an instance (e.g. 
C().f()). Both the class and the instance are ignored, and neither is passed 
implicitly as the first argument to the method.

--
assignee: docs@python
components: Documentation
messages: 306489
nosy: docs@python, haikuginger
priority: normal
pull_requests: 4391
severity: normal
status: open
title: Clarify the behavior of the staticmethod builtin
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com