You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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. :-)
Activity
tiran commentedon Nov 24, 2007
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
gvanrossum commentedon Nov 24, 2007
I'm waiting for those failing tests to magically start passing. :-)
tiran commentedon Nov 24, 2007
Do you still believe in the tooth fairy, too? :p
birkenfeld commentedon Nov 24, 2007
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.
birkenfeld commentedon Nov 24, 2007
Got test_typechecks too - the test is simply not applicable anymore.
birkenfeld commentedon Nov 24, 2007
Okay, got test_descr too -- the problem was introduced by the patch
itself :)
tiran commentedon Nov 24, 2007
Georg Brandl wrote:
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
birkenfeld commentedon Nov 24, 2007
I think it is correct -- normally the __get__ call gets a second
argument of C.
tiran commentedon Nov 25, 2007
Fixed in r59183
unittest was pretty tricky.
gvanrossum commentedon Nov 26, 2007
On Nov 24, 2007 11:37 AM, Christian Heimes <report@bugs.python.org> wrote:
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. :-)