Re: Confusion over calling a nested function inside a parent function

2006-12-23 Thread Bruno Desthuilliers
Pyenos a écrit : > [code] You already got the answer - just a pair of stylistic advices: > class WORK: 1/ By convention, ALL_UPPER names denote (pseudo) symbolic constants. The convention for class names is CamelCase. 2/ better to use new-style classes. => class Work(object): ... -- http:

Re: Confusion over calling a nested function inside a parent function

2006-12-23 Thread Bruno Desthuilliers
MacDonald a écrit : > Pyenos wrote: > >>[code] >>class WORK: >>def getwork(self): >>def choosetable(self):pass >>choosetable() #TypeError: choosetable() takes exactly 1 >> #argument (0 given) >>[/code] >> >>Calling choosetable() at the above location gives

Re: Confusion over calling a nested function inside a parent function

2006-12-22 Thread Pyenos
"MacDonald" <[EMAIL PROTECTED]> writes: > Pyenos wrote: > > [code] > > class WORK: > > def getwork(self): > > def choosetable(self):pass > > choosetable() #TypeError: choosetable() takes exactly 1 > > #argument (0 given) > > [/code] > > > > Calling chooset

Re: Confusion over calling a nested function inside a parent function

2006-12-22 Thread Duncan Booth
Pyenos <[EMAIL PROTECTED]> wrote: > [code] > class WORK: > def getwork(self): > def choosetable(self):pass > choosetable() #TypeError: choosetable() takes exactly 1 > #argument (0 given) > [/code] > > Calling choosetable() at the above location gives me t

Re: Confusion over calling a nested function inside a parent function

2006-12-22 Thread MacDonald
Pyenos wrote: > [code] > class WORK: > def getwork(self): > def choosetable(self):pass > choosetable() #TypeError: choosetable() takes exactly 1 > #argument (0 given) > [/code] > > Calling choosetable() at the above location gives me the error > described