>> Thanks; the __future__ import in 2.6 sounds great. > > I'm working on it. However it's not as easy as we first thought. BTW, did you see parser.c:future_hack? Regards, Martin