This is definitely fixable. If it doesn't get tackled before the PyCon sprint, it will undoubtedly get tackled then.
Kevin On 1/4/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > > Debugging is certainly painful even without TG getting in the way. > > The only crude way to debug actual Kid errors so far is a trial-and-run > approach with cutting suspicious blocks of code. > > I've documented my experience here: > http://max.textdriven.com/blog/entries/69/debugging-kid-templates-and-leaking-abstractions/ > > Regards, > Max. > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
