"Björn Lindström" schrieb
>
> > A great analysis, but what's a "pogo stick" and where can I get
one?
>
> http://search.ebay.com/pogo-stick
>
Yes, that explains the "bouncing with the pogo stick"; I would have
poked around
with a stick.
ROTFL, thank you.
Martin
--
http://mail.python.org/mailma
"Martin Blume" <[EMAIL PROTECTED]> writes:
> A great analysis, but what's a "pogo stick" and where can I get one?
http://search.ebay.com/pogo-stick
--
Björn Lindström <[EMAIL PROTECTED]>
Student of computational linguistics, Uppsala University, Sweden
--
http://mail.python.org/mailman/listinfo
"John Machin" schrieb
>
> [analysis of super() "oddness"]
>
A great analysis, but what's a "pogo stick" and where
can I get one?
Thanks
Martin
--
http://mail.python.org/mailman/listinfo/python-list
On 18/06/05 Diez B. Roggisch said:
> Certainly a bug - but not in python. The super-method works for
> new-style classes only.
>
> The attached script reproduces your observed behaviour. So kit seems
> that whatever toolkit you use, it uses new-style classes on windows, and
> old-style ones on
Michael P. Soulier wrote:
> Ok, this works in Python on Windows, but here on Linux, with Python 2.4.1, I'm
> getting an error.
>
> The docs say:
>
> A typical use for calling a cooperative superclass method is:
>
> class C(B):
> def meth(self, arg):
> super(C, self).meth(arg)
>
> H
Michael P. Soulier wrote:
Why the difference? Is Python portability overrated? Is this a bug?
Certainly a bug - but not in python. The super-method works for
new-style classes only.
The attached script reproduces your observed behaviour. So kit seems
that whatever toolkit you use, it uses n
