'class' argument optional for new.instancemethod?

[Martin Miller]

In section "3.27 new -- Creation of runtime internal objects" of the
documentation that comes with Python 2.4 it says:

instancemethod(function, instance, class)

This function will return a method object, bound to instance, or unbound if
instance is None. function must be callable.

However, some simple experiments I've tried seem to indicate that the
last argument, 'class' can be left off with no ill effects, and is
therefore optional.

Doesn't anyone know if this is a documention problem? Personally, I
don't understand how the argument gets used when it *is* provided -- if
nothing else, having it seems somewhat redundant given the presence of
the 'instance' argument.

TIA,
Martin

 

[Peter Hansen]

In section "3.27 new -- Creation of runtime internal objects" of the
documentation that comes with Python 2.4 it says:

instancemethod(function, instance, class)

[...]
However, some simple experiments I've tried seem to indicate that the
last argument, 'class' can be left off with no ill effects, and is
therefore optional.

Doesn't anyone know if this is a documention problem? Personally, I
don't understand how the argument gets used when it *is* provided -- if
nothing else, having it seems somewhat redundant given the presence of
the 'instance' argument.

A little experimentation reveals at least one thing that
argument affects:
.... pass
........ pass
........ print 'in f', self
....<bound method ?.f of <__main__.A instance at 0x00AE5EB8>>

So without the class argument, at least in this small
sample, the bound method doesn't know what class
it belongs to, at least for purposes of printing
it's own repr().

-Peter