im_function --> im_func

This commit is contained in:
Fred Drake 1998-08-07 16:28:13 +00:00
parent 60c3cafc24
commit 70da192f63
1 changed files with 2 additions and 2 deletions

View File

@ -420,10 +420,10 @@ is the instance, and the method object is said to be bound. For
instance, when \code{C} is a class which contains a definition for a
function \code{f}, \code{C.f} does not yield the function object
\code{f}; rather, it yields an unbound method object \code{m} where
\code{m.im_class} is \code{C}, \code{m.im_function} is \code{f}, and
\code{m.im_class} is \code{C}, \code{m.im_func} is \code{f}, and
m\code{.im_self} is \code{None}. When \code{x} is a \code{C}
instance, \code{x.f} yields a bound method object \code{m} where
m\code{.im_class} is \code{C}, \code{m.im_function} is \code{f}, and
m\code{.im_class} is \code{C}, \code{m.im_func} is \code{f}, and
\code{m.im_self} is \code{x}.
When an unbound user-defined method object is called, the underlying