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/2005-November/058184.html below:

[Python-Dev] Problems with the Python Memory Manager

[Python-Dev] Problems with the Python Memory Manager [Python-Dev] Problems with the Python Memory ManagerFredrik Lundh fredrik at pythonware.com
Thu Nov 17 09:44:06 CET 2005
Travis Oliphant wrote:

> Bingo.  Yes, definitely allocating new _types_ (an awful lot of them...)
> --- that's what the "array scalars" are: new types created in C.

are you allocating PyTypeObject structures dynamically?

why are you creating an awful lot of new type objects to represent the
contents of a homogenous array?

> If they don't get properly collected then that would definitely have
> created the problem.  It would seem this should be advertised when
> telling people to use PyObject_New for allocating new memory for
> an object.

PyObject_New creates a new instance of a given type; it doesn't, in itself,
create a new type.

at this point, your description doesn't make much sense.  more information
is definitely needed...

</F> 



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