OK, I'm currently checking in the fixes you suggested on the trunk. Too bad we cannot write a unit test that checks for memory leaks.

Jim, Graham, what shall we do for the 3.2.9 release ? Shall we keep on with the current branch or backport the fixes ?

Regards,
Nicolas

2006/7/9, Harold Ship <[EMAIL PROTECTED]>:

I've made a test build based on 3.2.8 release, where I've added Py_XDECREF()
calls in parse_qsl(), cfgtree_walk() TWICE (one on t, one on child), and
req_readlines().

My foo/bar program doesn't leak, and I'm now testing my full application. So
far, it seems to be ok.


Harold




Reply via email to