diff options
Diffstat (limited to 'docs/release-notes/version-4.9.1.rst')
| -rw-r--r-- | docs/release-notes/version-4.9.1.rst | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/docs/release-notes/version-4.9.1.rst b/docs/release-notes/version-4.9.1.rst index 7177274..d80efbc 100644 --- a/docs/release-notes/version-4.9.1.rst +++ b/docs/release-notes/version-4.9.1.rst @@ -16,8 +16,8 @@ Features Changed Because of changes in Python 3.9, and possibly because mod_wsgi makes use of externally created C threads to handle requests, and not Python native - threads, there is now a possibility that attempting to delete Python sub - interpreters will hang. It is believed this may relate to Python core now + threads, there is now a suspiscion that attempting to delete Python sub + interpreters can hang. It is believed this may relate to Python core now expecting all Python thread state objects to have been deleted before the Python sub interpreter can be destroyed. If they aren't then Python core code can block indefinitely. If the issue isn't the externally created C @@ -44,12 +44,12 @@ Features Changed attempt to delete the Python thread state objects before deleting the Python sub interpreter. - Because of this, from this version of mod_wsgi onwards, there will be no - attempt to destroy the Python sub interpreters or the main Python - interpreter when the process is being shutdown. As this means that - ``atexit`` registered callbacks will no longer be called, it is important - that you use mod_wsgi's own mechanism of being notified when a process is - being shutdown to perform any special actions. + Because of this uncertainty mod_wsgi now provides a way to disable the attempt + to destroy the Python sub interpreters or the main Python interpreter when the + process is being shutdown. This will though mean that ``atexit`` registered + callbacks will not be called if this option is enabled. It is therefore + important that you use mod_wsgi's own mechanism of being notified when a + process is being shutdown to perform any special actions. :: @@ -73,12 +73,11 @@ Features Changed actions on process shutdown. If you are affected, you should use mod_wsgi's mechanism to perform special actions on process shutdown. - If for some reason you want to revert to the prior behavior and have - mod_wsgi attempt to destroy any Python sub interpreters and the main Python - interpreter on process shutdown and you are manually configuring Apache, you - can add at global scope in the Apache configuration:: + If you need to enable this mode whereby no attempt is made to destroy the + Python interpreter (including sub interpreters) on process shutdown, you can + add at global scope in the Apache configuration:: - WSGIDestroyInterpreter On + WSGIDestroyInterpreter Off If you are using mod_wsgi-express, you can instead supply the command line - option ``--destroy-interpreter``.
\ No newline at end of file + option ``--orphan-interpreter``. |