Uh oh!
There was an error while loading. Please reload this page.
bpo-36356: Destroy the GIL at exit - #12453
Conversation
vstinner
commented
Mar 20, 2019
Failure on AppVeyor: |
vstinner
commented
Apr 26, 2019
PR #12667 might help to make Python more reliable with this change. |
vstinner
commented
Apr 26, 2019
With this change, test_tracemalloc fails because pymain_exit_error() tries to cleanup too many things, even for errors. I wrote PR #12968 to leave the runtime alive on this case, it fix test_tracemalloc. |
vstinner
commented
Apr 26, 2019
I merged my PR #12968 and rebased this PR on top of it. It should fix test_tracemalloc. |
vstinner
commented
Apr 26, 2019
The Ubuntu PR Tests Job of Azure Pipelines PR failed with: |
vstinner
commented
Apr 26, 2019
I don't understand test_io failuire. I prefer to wait until PR #12667 is merged to see if it does fix this issue. In the meanwhile, I put this issue again in WIP state. |
* Add _PyEval_FiniThreads2(). _PyEval_FiniThreads() now only clears the pending lock, whereas _PyEval_FiniThreads2() destroys the GIL. * pymain_free() now calls _PyEval_FiniThreads2(). * Py_FinalizeEx() now calls _PyEval_FiniThreads().
vstinner
commented
Apr 29, 2019
I merged PR #12667 and then rebased this PR on top of it. |
bedevere-bot
commented
Apr 29, 2019
|
bedevere-bot
commented
Apr 29, 2019
|
the pending lock, whereas _PyEval_FiniThreads2() destroys the GIL.
https://bugs.python.org/issue36356