From: R David Murray Date: Sun, 18 Dec 2016 19:59:58 +0000 (-0500) Subject: #29005: clarify terminology in tutorial 'method' discussion. X-Git-Tag: v3.5.3rc1~50 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4ec1590fbf584cbe328230c7b06c64db9b6e3842;p=thirdparty%2FPython%2Fcpython.git #29005: clarify terminology in tutorial 'method' discussion. Patch by Jim Fasarakis-Hilliard. --- diff --git a/Doc/tutorial/classes.rst b/Doc/tutorial/classes.rst index 75c79d252608..e134d5d62ea6 100644 --- a/Doc/tutorial/classes.rst +++ b/Doc/tutorial/classes.rst @@ -374,11 +374,11 @@ Surely Python raises an exception when a function that requires an argument is called without any --- even if the argument isn't actually used... Actually, you may have guessed the answer: the special thing about methods is -that the object is passed as the first argument of the function. In our +that the instance object is passed as the first argument of the function. In our example, the call ``x.f()`` is exactly equivalent to ``MyClass.f(x)``. In general, calling a method with a list of *n* arguments is equivalent to calling the corresponding function with an argument list that is created by inserting -the method's object before the first argument. +the method's instance object before the first argument. If you still don't understand how methods work, a look at the implementation can perhaps clarify matters. When an instance attribute is referenced that isn't a @@ -906,4 +906,3 @@ Examples:: namespace; the name :attr:`~object.__dict__` is an attribute but not a global name. Obviously, using this violates the abstraction of namespace implementation, and should be restricted to things like post-mortem debuggers. -