[Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation? (original) (raw)
Neil Schemenauer nas@python.ca
Tue, 19 Mar 2002 06:59:54 -0800
- Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Next message: [Python-Dev] generalized resource alloc and de-alloc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Skip Montanaro wrote:
Neil S. reported on a number of 3rd party extension modules that don't do object alloc/free properly. I reported a bug to the mysql-python project, which uses PyObjectNEW and PyMemFree. Andy Dustman's reply, in part, was:
1.5.2 apparently does not have PyObjectNew() or PyObjectDel(), thus the problem...
I don't consider extension modules that use PyObject_NEW and PyMem_DEL broken. The used to be the recommended way of doing it. We can't change that until at least Python 3.0.
Neil
- Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Next message: [Python-Dev] generalized resource alloc and de-alloc
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]