Of course I did recompile matplotlib to use the recompiled python with debug ABI. I just don't understand why if something is not leaded why a memleak has to happen.

Anyway, now my application using the recompiled matplotlib baffled this through valgrind as well. An there was no ImportError: ;-)


==17489== 40 bytes in 1 blocks are definitely lost in loss record 718 of 5,487
==17489==    at 0x4C2C63B: malloc (vg_replace_malloc.c:270)
==17489==    by 0x4EF1E8C: PyMem_Malloc (object.c:2343)
==17489==    by 0x10064848: initialize_builtin_datetime_metadata (arraytypes.c.src:3953)
==17489==    by 0x100719E2: set_typeinfo (arraytypes.c.src:4047)
==17489==    by 0x1016354E: initmultiarray (multiarraymodule.c:4057)
==17489==    by 0x4FB2661: _PyImport_LoadDynamicModule (importdl.c:53)
==17489==    by 0x4FAE3A7: load_module (import.c:1915)
==17489==    by 0x4FB07C1: import_submodule (import.c:2700)
==17489==    by 0x4FAFCC6: load_next (import.c:2515)
==17489==    by 0x4FAED8B: import_module_level (import.c:2224)
==17489==    by 0x4FAF320: PyImport_ImportModuleLevel (import.c:2288)
==17489==    by 0x4F78862: builtin___import__ (bltinmodule.c:49)


This is probably because I also added --without-pymalloc as you wanted.