This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alex Brandt
Recipients Alex Brandt, gvanrossum, vstinner, yselivanov
Date 2016-01-16.19:06:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452971166.69.0.340450798134.issue26133@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-01-16 19:06:06Alex Brandtsetrecipients: + Alex Brandt, gvanrossum, vstinner, yselivanov
2016-01-16 19:06:06Alex Brandtsetmessageid: <1452971166.69.0.340450798134.issue26133@psf.upfronthosting.co.za>
2016-01-16 19:06:06Alex Brandtlinkissue26133 messages
2016-01-16 19:06:06Alex Brandtcreate