2013/6/13 Nick Coghlan :
> Yes, that sounds better. One of the biggest problems with the current
> startup sequence is the way it relies on environment variables for
> configuration, which makes life hard for other applications that want to
> embed the CPython runtime.
I wrote a new patch (attache
On 13 Jun 2013 10:09, "Victor Stinner" wrote:
>
> 2013/6/13 Nick Coghlan :
> > On 13 Jun 2013 09:09, "Victor Stinner" wrote:
> >> Using this patch, detecting memory corruptions (buffer underflow and
> >> overflow) can be done without recompilation. We may add an environment
> >> variable to enabl
2013/6/13 Nick Coghlan :
> On 13 Jun 2013 09:09, "Victor Stinner" wrote:
>> Using this patch, detecting memory corruptions (buffer underflow and
>> overflow) can be done without recompilation. We may add an environment
>> variable to enable Python debug functions at runtime, example:
>> PYDEBUGMAL
On 13 Jun 2013 09:09, "Victor Stinner" wrote:
>
> Hi,
>
> I would like to improve memory allocators of Python. My two use cases
> are replacing memory allocators with custom allocators in embedded
> system and hooking allocators to track usage of memory.
>
> I wrote a patch for this, I'm going to
Hi,
I would like to improve memory allocators of Python. My two use cases
are replacing memory allocators with custom allocators in embedded
system and hooking allocators to track usage of memory.
I wrote a patch for this, I'm going to commit it if nobody complains:
http://bugs.python.org/issue33
