This is kind of surprising given that CPython uses its own ad-hoc allocator (see http://docs.python.org/release/2.3.5/whatsnew/section-pymalloc.html http://doc

This is kind of surprising given that CPython uses its own ad-hoc allocator (see http://docs.python.org/release/2.3.5/whatsnew/section-pymalloc.html http://docs.python.org/release/2.3.5/whatsnew/section-pymall...) which resorts to malloc() only for large chunks of memory and buffers... I wonder what's happening there.