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 vstinner
Recipients njs, pitrou, serhiy.storchaka, vstinner
Date 2017-12-11.19:36:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwa7r3y+KMMVZWTbFsTDj1dsyWxGjjYPyTQnr4n7kn0siw@mail.gmail.com>
In-reply-to <1513017498.25.0.213398074469.issue30050@psf.upfronthosting.co.za>
Content
As I wrote, I never saw this warning, even while debugging signal issues in
asyncio on FreeBSD. I don't think that this is an use case for a callback.
Nathaniel use case is just to ignore the warning, I consider that it's a
reasonable compromise for the issue.

If someone wants a more advanced signal handler, it's still possible to use
register a custom signal handler at the C level.
History
Date User Action Args
2017-12-11 19:36:53vstinnersetrecipients: + vstinner, pitrou, njs, serhiy.storchaka
2017-12-11 19:36:53vstinnerlinkissue30050 messages
2017-12-11 19:36:53vstinnercreate