我试图编写一个SIGTERM处理程序,让我的永远运行(-loop
这是我写的一个学习演示:
import asyncio
import signal
import logging
logging.basicConfig(level=logging.INFO, format='%(asctime)s %(levelname)s [%(name)s]: %(message)s', datefmt='%H:%M:%S')
_log = logging.getLogger(__name__)
class Looper:
def __init__(self, loop):
self._loop = loop
self._shutdown = False
signal.signal(signal.SIGINT, self._exit)
signal.signal(signal.SIGTERM, self._exit)
def _exit(self, sig, frame):
name = signal.Signals(sig).name
_log.info(f"Received shutdown-signal: {sig} ({name})")
self._shutdown = True
self._loop.stop() # << Stopping the event loop here.
_log.info(f"Loop stop initiated.")
pending = asyncio.all_tasks(loop=self._loop)
_log.info(f"Collected {len(pending)} tasks that have been stopped.")
if pending:
_log.info("Attempting to gather pending tasks: " + str(pending))
gatherer_set = asyncio.gather(*pending, loop=self._loop)
# self._loop.run_until_complete(gatherer_set) # << "RuntimeError: This event loop is already running"
_log.info("Shutting down for good.")
async def thumper(self, id, t):
print(f"{id}: Winding up...")
while not self._shutdown:
await asyncio.sleep(t)
print(f'{id}: Thump!')
print(f'{id}: Thud.')
loop = asyncio.get_event_loop()
lp = Looper(loop)
loop.create_task(lp.thumper('North Hall', 2))
loop.create_task(lp.thumper('South Hall', 3))
loop.run_forever()
_log.info("Done.")
在Windows10和Debian10上,上面的脚本都会对SIGINT作出反应并生成输出
North Hall: Winding up...
South Hall: Winding up...
North Hall: Thump!
South Hall: Thump!
North Hall: Thump!
South Hall: Thump!
North Hall: Thump!
09:55:53 INFO [__main__]: Received shutdown-signal: 2 (SIGINT)
09:55:53 INFO [__main__]: Loop stop initiated.
09:55:53 INFO [__main__]: Collected 2 tasks that have been stopped.
09:55:53 INFO [__main__]: Attempting to gather pending tasks: {<Task pending coro=<Looper.thumper() running at amazing_grace.py:42> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x02F91BF0>()]>>, <Task pending coro=<Looper.thumper() running at amazing_grace.py:42> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x02F91C10>()]>>}
09:55:53 INFO [__main__]: Shutting down for good.
09:55:53 INFO [__main__]: Done.
不幸的是,“砰”一行表示砰砰(…)演示调用实际上 结论是,不会出现。我猜,这是因为“聚会”给了我一套 未实现的未来。但是,如果我敢激活则运行直到完成()- 行,即使它位于self.\u loop.stop()之后,输出 结束如下:
[...]
10:24:25 INFO [__main__]: Collected 2 tasks that have been stopped.
10:24:25 INFO [__main__]: Attempting to gather pending tasks: {<Task pending coro=<Looper.thumper() running at amazing_grace.py:41> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x03E417D0>()]>>, <Task pending coro=<Looper.thumper() running at amazing_grace.py:41> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x03E41BF0>()]>>}
Traceback (most recent call last):
File "amazing_grace.py", line 50, in <module>
loop.run_forever()
File "C:\Python37\lib\asyncio\base_events.py", line 539, in run_forever
self._run_once()
File "C:\Python37\lib\asyncio\base_events.py", line 1739, in _run_once
event_list = self._selector.select(timeout)
File "C:\Python37\lib\selectors.py", line 323, in select
r, w, _ = self._select(self._readers, self._writers, [], timeout)
File "C:\Python37\lib\selectors.py", line 314, in _select
r, w, x = select.select(r, w, w, timeout)
File "amazing_grace.py", line 35, in _exit
self._loop.run_until_complete(gatherer_set) # << "This event loop is already running"
File "C:\Python37\lib\asyncio\base_events.py", line 571, in run_until_complete
self.run_forever()
File "C:\Python37\lib\asyncio\base_events.py", line 526, in run_forever
raise RuntimeError('This event loop is already running')
RuntimeError: This event loop is already running
问题归结为
该程序应在Python 3.7上运行,同时在Windows 10和Linux下运行
正如zaquest在回答中所说的那样,如果只是分配一个信号处理程序并在其中添加一个create_task
调用,就会自找麻烦;正如我观察到的,这个例程可能运行,也可能不运行(即使没有其他任务)。因此,现在我添加了一个sys.platform
检查脚本是否在UNIX()下运行。如果是的话,我更喜欢使用更可靠的loop.add_signal_handler
来定义回调函数,这正是我真正需要的。幸运的是,UNIX是我的主要用例。主线:
self._loop.add_signal_handler(signal.signal(signal.SIGINT, self._exit, signal.SIGINT, None)
为什么要进行平台检查?:在文档https://docs.python.org/3/library/asyncio-eventloop.html#unix-signals之后,loop.add_signal_handler()在Windows上不可用,考虑到所讨论的信号是UNIX行话,这并不奇怪
Python信号处理程序在main thread中执行,在循环运行的同一线程中执行
BaseEventLoop.stop()
方法不会立即停止循环,而只是sets a flag,这样当下次循环运行时,它只执行已经调度的回调,而不会调度更多的回调(请参见run_forever)。但是,在信号处理程序返回之前,循环无法运行。这意味着您不能等到循环在信号处理程序中停止。相反,您可以安排另一个任务,等待长时间运行的任务对self._shutdown
中的更改做出反应,然后停止循环还有一件事需要提到的是,文档中说
signal.signal()
处理程序是not allowed
与循环交互的,但没有说明原因(see)找到一个将从异步函数调用self.\u loop.stop()的解决方案 这将首先等待所有其他任务。请注意,它不会等待自己! 如果它尝试,程序将锁定
此外,asyncio.wait_for(..)co例程允许超时
在Windows 10上,这可能导致输出
失败的进程受到超时的影响
请注意,这解决了我的问题。但是,调用loop.stop()后,为什么loop.run\u直到\u complete(..)失败的问题仍然存在
相关问题 更多 >
编程相关推荐