-
-
Notifications
You must be signed in to change notification settings - Fork 34k
gh-139391: properly handle signal.signal() in UnixConsole when called from a non-main thread
#139392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: yihong0618 <zouzou0208@gmail.com>
Signed-off-by: yihong0618 <zouzou0208@gmail.com> Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
signal.signal() in UnixConsole when called from a non-main thread
Signed-off-by: yihong0618 <zouzou0208@gmail.com>
Misc/NEWS.d/next/Library/2025-09-28-16-34-11.gh-issue-139391.nRFnmx.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Signed-off-by: yihong0618 <zouzou0208@gmail.com>
|
I'll wait for @ambv to review this as well. |
Thank you very much! |
Signed-off-by: yihong0618 <zouzou0208@gmail.com>
|
Thanks @yihong0618 for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
GH-139858 is a backport of this pull request to the 3.14 branch. |
|
Thanks @yihong0618 for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Sorry, @yihong0618 and @kumaraditya303, I could not cleanly backport this to |
|
GH-139861 is a backport of this pull request to the 3.13 branch. |
…sole` when called from a non-main thread (pythonGH-139392) (cherry picked from commit b8c8b8f) Co-authored-by: yihong <zouzou0208@gmail.com>
…hen called from a non-main thread (pythonGH-139392) (cherry picked from commit b8c8b8f) Co-authored-by: yihong <zouzou0208@gmail.com>
after this patch it goes normal with ctrl+z and fg
python -m asyncioprocess is not properly handled on Unix-like platforms #139391