homepage

Here is a first patch to remove unbound method objects.
6 tests failed:
 test_descr test_inspect test_pyclbr test_typechecks test_unittest
 test_weakref

I'm waiting for those failing tests to magically start passing. :-)

Do you still believe in the tooth fairy, too? :p

Okay, this new patch takes care of test_pyclbr, test_inspect and
test_weakref.
test_unittest is a bit hard:
previously, calling loadTestsFromName with the name of a method would
create a test that runs that test case with that method being the test
method. With the name of a staticmethod though it would call the
staticmethod first and use the result of that call as the test case.
Now, there is no visible distinction between static methods and normal
methods anymore.

Got test_typechecks too - the test is simply not applicable anymore.

Okay, got test_descr too -- the problem was introduced by the patch
itself :)

Georg Brandl wrote:
> Okay, got test_descr too -- the problem was introduced by the patch
> itself :)
Yes, I introduced the problem because I thought that sometimes is wrong
here. The question mark in <bound method ?.foo of <__main__.C object at
...>> doesn't look right.
Christian

I think it is correct -- normally the __get__ call gets a second
argument of C.

Fixed in r59183
unittest was pretty tricky.

On Nov 24, 2007 11:37 AM, Christian Heimes <report@bugs.python.org> wrote:
> Do you still believe in the tooth fairy, too? :p
Yes, and in the Easter Bunny, Santa Claus, and Sinterklaas. But in
this particular case I believe in Kaboutertjes. (Dutch gnomes.) And it
turns out I was right. :-)