[Python-Dev] Possible bug in complexobject.c (still in Python 2.5) (original) (raw)
Travis E. Oliphant oliphant.travis at ieee.org
Thu Jun 1 06:27:40 CEST 2006
- Previous message: [Python-Dev] Possible bug in complexobject.c (still in Python 2.5)
- Next message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Travis E. Oliphant wrote:
I'm curious about the difference between
floatsubtypenew in floatobject.c complexsubtypefromccomplex in complexobject.c The former uses type->tpalloc(type, 0) to create memory for the object while the latter uses PyTypeGenericAlloc(type, 0) to create memory for the sub-type (thereby by-passing the sub-type's own memory allocator). It seems like this is a bug. Shouldn't type->tpalloc(type, 0) also be used in the case of allocating complex subtypes?
I submitted an entry and a patch for this on SourceForge Tracker (#1498638)
http://sourceforge.net/tracker/index.php?func=detail&aid=1498638&group_id=5470&atid=105470
-Travis
- Previous message: [Python-Dev] Possible bug in complexobject.c (still in Python 2.5)
- Next message: [Python-Dev] Let's stop eating exceptions in dict lookup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]