Message147555
Thanks for the comments, here is a new patch addressing them.
I've kept the C API available in all builds (since it's private), but sys.getallocatedblocks() is only available in debug builds.
As for the memory leak run results, I think we may have to devise a heuristic where results like [1,0,1] (or similar variation of 0s, 1s, and -1s) are considered a success, but others like [1,1,1] are a failure. |
|
Date |
User |
Action |
Args |
2011-11-13 16:27:30 | pitrou | set | recipients:
+ pitrou, tim.peters, ncoghlan, Trundle |
2011-11-13 16:27:30 | pitrou | set | messageid: <1321201650.05.0.752795585328.issue13390@psf.upfronthosting.co.za> |
2011-11-13 16:27:29 | pitrou | link | issue13390 messages |
2011-11-13 16:27:29 | pitrou | create | |
|