A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-June/065505.html below:

[Python-Dev] Possible bug in complexobject.c (still in Python 2.5)

[Python-Dev] Possible bug in complexobject.c (still in Python 2.5) [Python-Dev] Possible bug in complexobject.c (still in Python 2.5)Travis E. Oliphant oliphant.travis at ieee.org
Thu Jun 1 06:27:40 CEST 2006
Travis E. Oliphant wrote:
> I'm curious about the difference between
> 
> float_subtype_new  in floatobject.c
> complex_subtype_from_c_complex in complexobject.c
> 
> The former uses type->tp_alloc(type, 0) to create memory for the object
> while the latter uses PyType_GenericAlloc(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->tp_alloc(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

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4