RetroSearch Browse

Fri Mar 25 11:14:16 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/110066.html

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().

I can try to ensure that Python does restore all signals installed by
faulthandler and cancel the current alarm() (used by
dump_traceback_later()). Or I can hardcode something to unload
faulthandler in Py_FinalizeEx() (or somewhere else).

Victor

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/110066.html below:

[Python-Dev] Unload a module written in C