[New-bugs-announce] [issue32070] Clarify the behavior of the staticmethod builtin

Jesse SHapiro report at bugs.python.org
Sat Nov 18 13:04:15 EST 2017


New submission from Jesse SHapiro <jesse at jesseshapiro.net>:

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 at python
components: Documentation
messages: 306489
nosy: docs at python, haikuginger
priority: normal
pull_requests: 4391
severity: normal
status: open
title: Clarify the behavior of the staticmethod builtin
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32070>
_______________________________________


More information about the New-bugs-announce mailing list