On Sat, 02 Jun 2007 11:25:04 -0700, Warren Stringer wrote: > Since `a()` translates to `a() for a in b` then the error would be the exact > same `TypeError: 'str' object is not callable`
Not in any language called Python I know of. Supposedly 28 years programming experience, and you can't even see the _serious_ problems with "a()" --> "a() for a in b". Well, that explains a lot about the lousy state of so many programming projects. What's b? Given "a()", how does the compiler identify which b is the one to look at? How does the recursive reference to a() terminate? [snip] > For now, I am out of here! Please don't come back until you have a clue. -- Steven. -- http://mail.python.org/mailman/listinfo/python-list
