seb bacon wrote: > > can't help wondering if it's something to do with that py_malloc stuff > that's been floating around. Indeed. Steve A suggested that too, so what is this py_malloc mallarky and when's it gonna get fixed? cheers, Chris