[Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation? (original) (raw)
Skip Montanaro skip@pobox.com
Tue, 19 Mar 2002 07:33:06 -0600
- Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Next message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael> Better IMHO is what _sre.c does:
Michael> #if PY_VERSION_HEX < 0x01060000
Michael> #define PyObject_DEL(op) PyMem_DEL((op))
Michael> #endif
Thanks, I'll pass that along to Andy.
>> 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.
Michael> I thought we'd already worked this much out...
We might have, but clearly there are a lot of extension module writers who haven't. ;-)
Skip
- Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Next message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]