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/2002-April/022864.html below:

[Python-Dev] New type objects and PyObject_New

[Python-Dev] New type objects and PyObject_New [Python-Dev] New type objects and PyObject_NewThomas Heller thomas.heller@ion-tof.com
Tue, 9 Apr 2002 22:06:22 +0200
From: "Martin v. Loewis" <martin@v.loewis.de>
> "Thomas Heller" <thomas.heller@ion-tof.com> writes:
> 
> > It seems possible to create new type objects still with
> > PyObject_New() instead of calling the type object.
> > Is this a bug?
> 
> Not sure what you are asking: I assume you are *not* asking about new
> type objects (as created by typeobject.c:type_new), but instead about
> instance of newstyle classes (i.e. instance of type objects).
Correct.
> 
> Why would you then think that using PyObject_New is a bad thing?

IIUC, PyObject_New doesn't call the tp_new, tp_alloc, and tp_init slots.
So, the new object probably will be in an invalid state, may be
allocated by an allocator not compatible with the tp_dealloc slot?

> 
> Regards,
> Martin
> 
> 
Thanks,

Thomas





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