Message258401
When using the suggested practice of setting a stop loop signal handler with:
loop.add_signal_handler(signal.SIGTERM, loop.stop)
The following stack trace is given when the signal runs:
ligament_1 | Exception ignored in: <bound method BaseEventLoop.__del__ of <_UnixSelectorEventLoop running=False closed=True debug=False>>
ligament_1 | Traceback (most recent call last):
ligament_1 | File "/usr/lib/python3.5/asyncio/base_events.py", line 387, in __del__
ligament_1 | File "/usr/lib/python3.5/asyncio/unix_events.py", line 58, in close
ligament_1 | File "/usr/lib/python3.5/asyncio/unix_events.py", line 139, in remove_signal_handler
ligament_1 | File "/usr/lib/python3.5/signal.py", line 47, in signal
ligament_1 | TypeError: signal handler must be signal.SIG_IGN, signal.SIG_DFL, or a callable object
Since this happens during shutdown of the application I wouldn't consider this a high priority bug but it is quite annoying. I've also not investigated if this interrupts the loop stopping procedure yet. |
|
Date |
User |
Action |
Args |
2016-01-16 19:06:06 | Alex Brandt | set | recipients:
+ Alex Brandt, gvanrossum, vstinner, yselivanov |
2016-01-16 19:06:06 | Alex Brandt | set | messageid: <1452971166.69.0.340450798134.issue26133@psf.upfronthosting.co.za> |
2016-01-16 19:06:06 | Alex Brandt | link | issue26133 messages |
2016-01-16 19:06:06 | Alex Brandt | create | |
|