Alex wrote:
> On 5/15/06, bruno at modulix <[EMAIL PROTECTED]> wrote:
>
(snip)
>
> Thanks for taking your time to help me out. :) You have cleared out
> many of my doubts. BTW, should I post "thank you" stuff here
Ain't that what you just did ?-)
> or does
> it just clutter?
Nope, 'thank you
On 5/15/06, bruno at modulix <[EMAIL PROTECTED]> wrote:
> Alex wrote:
> > Hi, this is my first mail to the list so please correct me if Ive done
> > anything wrong.
> >
> > What Im trying to figure out is a good way to organise my code. One
> > class per .py file is a system I like, keeps stuff apa
> Some unbound method error. Have I missunderstood something or am I on
> the right track here?
You misunderstood that you'd have to create an instance first before
invoking a method on that very instance. That is the same in C++, btw.
> But in my opinion, this is very ugly. Especially if the cla
Alex wrote:
> Hi, this is my first mail to the list so please correct me if Ive done
> anything wrong.
>
> What Im trying to figure out is a good way to organise my code. One
> class per .py file is a system I like, keeps stuff apart. If I do
> that, I usually name the .py file to the same as the
On 2006-05-15, Alex <[EMAIL PROTECTED]> wrote:
import Foo
Foo.Foo.bar()
> Traceback (most recent call last):
> File "", line 1, in ?
> TypeError: unbound method bar() must be called with Foo instance as
> first argument (got nothing instead)
>
> ...
>
> One thing that I tried that work
Hi, this is my first mail to the list so please correct me if Ive done
anything wrong.
What Im trying to figure out is a good way to organise my code. One
class per .py file is a system I like, keeps stuff apart. If I do
that, I usually name the .py file to the same as the class in it.
File: Foo.
