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

Showing content from https://mail.python.org/pipermail/python-dev/2001-May/014868.html below:

[Python-Dev] GC and ExtensionClass - a summary of the problem and a workaround

• Previous message: [Python-Dev] GC and ExtensionClass - a summary of the problem and a workaround
• Next message: [Python-Dev] Re: GC and ExtensionClass - a summary of the problem and a workaround
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 17 May 2001, Fredrik Lundh wrote:

> footnote: this is usually done in the module init function, *before*
> the call to Py_InitModule.  see:

The PyExtensionClass_Export() function requires a pointer to the module
dictionary so that it can add itself to the module.  Unfortunately this
requires that Py_InitModule to have been called before hand.

I guess this means that the current ExtensionClass API will need to be
modified in order to allow ExtensionClasses to be initialised before
Py_InitModule.

>
>     http://www.python.org/doc/FAQ.html#3.24
>
> if the garbage collector can run after Python calls a module's init-
> function, but before that module calls back into Python, anything
> can happen...

James.

• Previous message: [Python-Dev] GC and ExtensionClass - a summary of the problem and a workaround
• Next message: [Python-Dev] Re: GC and ExtensionClass - a summary of the problem and a workaround
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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