This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Rhamphoryncus
Recipients Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, gvanrossum
Date 2008-01-17.23:34:30
SpamBayes Score 0.0277998
Marked as misclassified No
Message-id <>
PyGILState_Ensure WOULD block forever if it acquired the GIL before
doing anything else.

The only way to make Py_Initialize callable after Py_Finalize is to make
various bits of the finalization into no-ops.  For instance, it's
currently impossible to unload C extension modules, so they must be left
around permanently.  I'm not convinced it works currently, or that
there's use cases for it.

Note that unloading between Py_Finalize and Py_Initialize
would definitely break things, as you'd lose all the global variables
maintaining things.  That eliminates the only "it's more elegant" argument.
Date User Action Args
2008-01-17 23:34:33Rhamphoryncussetspambayes_score: 0.0277998 -> 0.0277998
recipients: + Rhamphoryncus, gvanrossum, gregory.p.smith, amaury.forgeotdarc
2008-01-17 23:34:33Rhamphoryncussetspambayes_score: 0.0277998 -> 0.0277998
messageid: <>
2008-01-17 23:34:31Rhamphoryncuslinkissue1856 messages
2008-01-17 23:34:30Rhamphoryncuscreate