-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Handle SIGTERM in asyncio #125688
Labels
Comments
cc @graingert, you're better at dealing with asyncio stuff than I am. |
cpython doesn't define a handler for SIGTERM for synchronous code, so I don't think asyncio should either |
ZeroIntensity
added
the
pending
The issue will be closed if no feedback is provided
label
Oct 18, 2024
Let's close this for now |
ZeroIntensity
removed
the
pending
The issue will be closed if no feedback is provided
label
Oct 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature or enhancement
Proposal:
#32105 did introduce handling of
SIGINT
signals inasyncio.run()
. I think it makes sense to support handling ofSIGTERM
signals in the same way as both signals are intended for shutting down a process gracefully.SIGTERM
is also the default signal to stop a container: https://docs.docker.com/reference/cli/docker/container/stop/Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered: