A
Armin Steinhoff
Hi all,
I'm just porting a piece of python code for using a different
database.
When I run the original version .. the type of 'set' is a tuple ...
and is magically in the new version a 'class instance'. The code is
the same in both versions:
ins_list = [(0,1,2,3),]
self.IMpos =0
for set in ins_list:
setdata = (self.IMpos,) + set[1:]
Any ideas why set is treated as a 'tuple' and in the other case as a
'class instance' ?? (Python 2.3.3 )
Regards
Armin
I'm just porting a piece of python code for using a different
database.
When I run the original version .. the type of 'set' is a tuple ...
and is magically in the new version a 'class instance'. The code is
the same in both versions:
ins_list = [(0,1,2,3),]
self.IMpos =0
for set in ins_list:
setdata = (self.IMpos,) + set[1:]
Any ideas why set is treated as a 'tuple' and in the other case as a
'class instance' ?? (Python 2.3.3 )
Regards
Armin