Steve Holden wrote: > Robin Becker wrote: ....... >> Has anyone got any clue what the problem might be or a fixed version of the >> code? > > I'm guessing this might be to do with the changes that have been made to > enable 64-bit readiness in the code, but I couldn't suggest specifics. > > Suspect all pointers and integers first :-) ..... Indeed Steve, but it was in fact PyMem_DEL vs PyObject_NEW. Just replaced three PyMem_DEL's with PyObject_FREE and things now work again. The free I suspected wasn't involved at all. -- Robin Becker
-- http://mail.python.org/mailman/listinfo/python-list
