[issue3329] API for setting the memory allocator used by Python

2009-01-07 Thread Jukka Laurila
Jukka Laurila added the comment: Brett is right. Macroing the memory allocator is a better choice than forcing indirection on all platforms. We did this on Python for S60, using the macros PyCore_{MALLOC,REALLOC,FREE}_FUNC for interpreter's allocations, and then redirected those to a mech

[issue3329] API for setting the memory allocator used by Python

2008-07-10 Thread Jukka Laurila
Jukka Laurila <[EMAIL PROTECTED]> added the comment: Brett, the ability to define the allocator dynamically at runtime could be a compile time option, turned on by default only on small memory platforms. On most platforms you can live with plain old malloc and may want to avoid the indir

[issue3329] API for setting the memory allocator used by Python

2008-07-09 Thread Jukka Laurila
New submission from Jukka Laurila <[EMAIL PROTECTED]>: Currently Python always uses the C library malloc/realloc/free as the underlying mechanism for requesting memory from the OS, but especially on memory-limited platforms it is often desirable to be able to override the allocator

[issue1783] nonexistent data items declared as exports in sysmodule.h

2008-01-10 Thread Jukka Laurila
New submission from Jukka Laurila: sysmodule.h contains the following declarations for data to be exported from the Python DLL, but these variables don't seem to exist anywhere: PyAPI_DATA(PyObject *) _PySys_TraceFunc, *_PySys_ProfileFunc; PyAPI_DATA(int) _PySys_CheckInterval; Eithe