On Dec 31, 2010, at 8:06 PM, DenesL wrote: > >> The ideal solution would be one that allowed using T() normally in gluon (at >> least in code that's invoked from an application); that avoids the T=T >> requirement. >> >> My conjecture is when Python compiles the gluon code, it binds T references >> (to what? that's the hole in my theory) at compile time, and thus ignores >> the presence of T in globals. Making T an argument forces Python to defer >> binding. >> > The funny part is that T is in environment (!!!?) so > exec ccode in environment > should work, I don't see why it does not. >
Neither do I, but I think that T must already be bound (to what? dunno), before the environment is created.
