Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[3.6] bpo-26558: Fix Py_FatalError() with GIL released (GH-10267)#10270

Merged
vstinner merged 1 commit intopython:3.6python/cpython:3.6from
vstinner:fatal_error36Copy head branch name to clipboard
Nov 1, 2018
Merged

[3.6] bpo-26558: Fix Py_FatalError() with GIL released (GH-10267)#10270
vstinner merged 1 commit intopython:3.6python/cpython:3.6from
vstinner:fatal_error36Copy head branch name to clipboard

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented Oct 31, 2018

Don't call _Py_FatalError_PrintExc() nor flush_std_files() if the
current thread doesn't hold the GIL, or if the current thread
has no Python state thread.

(cherry picked from commit 3a228ab)

https://bugs.python.org/issue26558

Don't call _Py_FatalError_PrintExc() nor flush_std_files() if the
current thread doesn't hold the GIL, or if the current thread
has no Python state thread.

(cherry picked from commit 3a228ab)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.