On Jun 18, 11:56 pm, nn <prueba...@latinmail.com> wrote: > On Jun 18, 8:38 am, guthrie <grguth...@gmail.com> wrote: > > > > > On Jun 17, 6:38 pm, Steven Samuel Cole <steven.samuel.c...@gmail.com> > > wrote: > > > > Still don't really understand why my initial code didn't work, though... > > > Your code certainly looks reasonable, and looks to me like it "should" > > work. The comment of partial namespace is interesting, but > > unconvincing (to me) - but I am not a Python expert! It would > > certainly seem that within that code block it is in the local > > namespace, not removed from that scope to be in another. > > > Seems that it should either be a bug, or else is a design error in the > > language! > > > Just as in the above noted "WTF" - non-intuitive language constructs > > that surprise users are poor design. > > This is certainly an odd one. This code works fine under 2.6 but fails > in Python 3.1. > > >>> class x: > > ... lst=[2] > ... gen=[lst.index(e) for e in lst] > ... > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "<stdin>", line 3, in x > File "<stdin>", line 3, in <listcomp> > NameError: global name 'lst' is not defined >
Arghh. I see thousands of future wtf!? posts to c.l.p. triggered by this new feature. Might as well save some time and add it to the FAQ already. -- http://mail.python.org/mailman/listinfo/python-list
