[Python-Dev] PEP 384 status (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Sep 1 00:48:37 CEST 2010
- Previous message: [Python-Dev] PEP 384 status
- Next message: [Python-Dev] Working on the Python code-base with a VIM-based setup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
M.-A. Lemburg wrote:
But isn't exactly that a major problem for Python ?
An extension written for a different MS CRT version would not be able to safely free a buffer allocated by the Python DLL.
Python provides its own set of memory alloc/free functions to deal with this exact problem. For every Python function that allocates something, there's a corresponding function for freeing it, and you do it any other way at your peril.
-- Greg
- Previous message: [Python-Dev] PEP 384 status
- Next message: [Python-Dev] Working on the Python code-base with a VIM-based setup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]