本文整理匯總了Python中gevent.signal_handler方法的典型用法代碼示例。如果您正苦於以下問題:Python gevent.signal_handler方法的具體用法?Python gevent.signal_handler怎麽用?Python gevent.signal_handler使用的例子?那麽, 這裏精選的方法代碼示例或許可以為您提供幫助。您也可以進一步了解該方法所在類gevent
的用法示例。
在下文中一共展示了gevent.signal_handler方法的3個代碼示例,這些例子默認根據受歡迎程度排序。您可以為喜歡或者感覺有用的代碼點讚,您的評價將有助於係統推薦出更棒的Python代碼示例。
示例1: install_signal_handlers
# 需要導入模塊: import gevent [as 別名]
# 或者: from gevent import signal_handler [as 別名]
def install_signal_handlers(self):
""" Handle events like Ctrl-C from the command line. """
self.graceful_stop = False
def request_shutdown_now():
self.shutdown_now()
def request_shutdown_graceful():
# Second time CTRL-C, shutdown now
if self.graceful_stop:
self.shutdown_now()
else:
self.graceful_stop = True
self.shutdown_graceful()
# First time CTRL-C, try to shutdown gracefully
gevent.signal_handler(signal.SIGINT, request_shutdown_graceful)
# User (or Heroku) requests a stop now, just mark tasks as interrupted.
gevent.signal_handler(signal.SIGTERM, request_shutdown_now)
示例2: __init__
# 需要導入模塊: import gevent [as 別名]
# 或者: from gevent import signal_handler [as 別名]
def __init__(self, settings):
self.settings = settings
self.start_time = None
self.end_time = None
gevent.signal_handler(signal.SIGTERM, sig_term_handler)
示例3: test_orphaned_signal_watcher
# 需要導入模塊: import gevent [as 別名]
# 或者: from gevent import signal_handler [as 別名]
def test_orphaned_signal_watcher(self):
# Install libev-based signal watcher.
try:
s = gevent.signal(signal.SIGTERM, signals_test_sigterm_handler)
except AttributeError:
# This function got renamed in gevent 1.5
s = gevent.signal_handler(signal.SIGTERM, signals_test_sigterm_handler)
# Normal behavior: signal handlers become inherited by children.
# Bogus behavior of libev-based signal watchers in child process:
# They should not be active anymore when 'orphaned' (when their
# corresponding event loop has been destroyed). What happens, however:
# The old handler stays active and registering a new handler does not
# 'overwrite' the old one -- both are active.
# Since this test is about testing the behavior of 'orphaned' libev
# signal watchers, the signal must be transmitted *after* event loop
# recreation, so wait here for the child process to go through
# the hub & event loop destruction (and recreation) process before
# sending the signal. Waiting is realized with sync through pipe.
# Without cleanup code in gipc, the inherited but orphaned libev signal
# watcher would be active in the fresh event loop and trigger the
# handler. This is a problem. With cleanup code, this handler must
# never be called. Child exitcode 20 means that the inherited handler
# has been called, -15 (-signal.SIGTERM) means that the child was
# actually killed by SIGTERM within a certain short time interval.
# Returncode 0 would mean that the child finished normally after that
# short time interval.
with pipe() as (r, w):
p = start_process(signals_test_child_a, (w,))
assert r.get() == p.pid
os.kill(p.pid, signal.SIGTERM)
p.join()
if not WINDOWS:
assert p.exitcode == -signal.SIGTERM
else:
assert p.exitcode == signal.SIGTERM
s.cancel()