[Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation? (original) (raw)

Skip Montanaro skip@pobox.com
Tue, 19 Mar 2002 01:22:17 -0600

1.5.2 rears its ugly head again...

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 PyObject_NEW and PyMem_Free. Andy Dustman's reply, in part, was:

1.5.2 apparently does not have PyObject_New() or PyObject_Del(), thus
the problem...

The thread is here:

http://sourceforge.net/tracker/?func=detail&atid=374932&aid=531671&group_id=22307

Check here for Andy's proposed patch to _mysql.c (ignore the non-alloc stuff):

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mysql-python/MySQLdb/_mysql.c.diff?r1=1.16&r2=1.22

It would appear at least some of the breakage stems from actual or perceived differences in the object allocation API between 1.5.2 and 2.x.

Skip