forked from goodboy/tractor
If the root calls `trio.Process.kill()` on immediate child proc teardown when the child is using pdb, we can get stdstreams clobbering that results in a pdb++ repl where the user can't see what's been typed. Not killing such children on cancellation / error seems to resolve this issue whilst still giving reliable termination. For now, code that special path until a time it becomes a problem for ensuring zombie reaps. |
||
|---|---|---|
| .. | ||
| testing | ||
| __init__.py | ||
| _actor.py | ||
| _child.py | ||
| _debug.py | ||
| _discovery.py | ||
| _entry.py | ||
| _exceptions.py | ||
| _forkserver_override.py | ||
| _ipc.py | ||
| _mp_fixup_main.py | ||
| _portal.py | ||
| _root.py | ||
| _spawn.py | ||
| _state.py | ||
| _streaming.py | ||
| _trionics.py | ||
| log.py | ||
| msg.py | ||