Message318454
To clarify this ticket: I'm talking about prohibiting `loop.add_signal_handler(SIGCHLD)` as it would break child processes watchers that asyncio installs. In other words, setting a custom SIGCHLD breaks asyncio internals.
We can allow user-set SIGCHLD signals if we add some code to make sure that 'add_signal_handler(SIGCHLD)' delivers the signal to *both* asyncio internals and user code. But I'm not sure if there's a valid use case for listening for SIGCHLD for user code at all.
For now, I disabled SIGCHLD in uvloop, let's see if people complain. |
|
Date |
User |
Action |
Args |
2018-06-01 19:00:39 | yselivanov | set | recipients:
+ yselivanov, gregory.p.smith, asvetlov |
2018-06-01 19:00:39 | yselivanov | set | messageid: <1527879639.57.0.81473610881.issue33650@psf.upfronthosting.co.za> |
2018-06-01 19:00:39 | yselivanov | link | issue33650 messages |
2018-06-01 19:00:39 | yselivanov | create | |
|