Nick Coghlan ncoghlan at gmail.com
Fri Mar 25 12:14:59 CET 2011

• Previous message: [Python-Dev] Unload a module written in C
• Next message: [Python-Dev] Unload a module written in C
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Fri, Mar 25, 2011 at 8:14 PM, Victor Stinner
<victor.stinner at haypocalc.com> wrote:
> Le vendredi 25 mars 2011 à 07:59 +0100, "Martin v. Löwis" a écrit :
>> > Is there a bug somewhere, or do I misunderstood something important?
>>
>> Module unloading is simply not implemented, and would be very difficult
>> to implement.
>
> My problem is that if Python is embeded, my module will still be active
> after Py_FinalizeEx(). For example, if it installed an handler for the
> SIGSEGV signal: a segmentation fault will call the handler which will
> try to get the interpreter state, but there is no more interpreter. I
> don't know if it is a problem or not, but I would prefer to cleanup my
> module on Py_FinalizeEx().

And registering your cleanup function with atexit() isn't enough? Or
does that remove the handler too early?

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message: [Python-Dev] Unload a module written in C
• Next message: [Python-Dev] Unload a module written in C
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list