Lawrence Chan

Sorry if I'm misreading something, but I think that commit bumps to prompt-toolkit v2 but this issue is about prompt-toolkit v3?

FYI 3.8 has the same symptom, but the fix is to change the `is_py37` check to something like ```python is_py37 = version_info[:2] >= (3, 7) ``` rather than the current...

If/when this gets attention, I think @diefans's solution using typing_inspect is the way to go. I wasn't aware that that package existed but that's a better long-term fix than my...

Okay with verbose logging enabled I now get what's happening. The main process spawns a subprocess which returns with 0, causing proot to set `last_exit_status=0`. Then when the main process...

If you run e.g. `proot sleep 60` and send a signal to the sleep process, it currently returns -1 regardless of the signal. It would be helpful to return something...

Try sending the signal to `$(pgrep sleep)` or somesuch, what we want is for inner signals to bubble up.

Not sure if these are the official docs, but it's mentioned [here](https://www.tldp.org/LDP/abs/html/exitcodes.html). So for example, if the process gets killed by SIGINT=2 or SIGSEGV=11, bash sets the returncode to `128...

Should I just update the example to be functionally the same but have an interpolated list name internally? In practice you probably wouldnt use it unless you have at least...

@mwchase I agree. With mypy v0.761 + CPython v3.7.4 I also get what you pasted above.

Totally understand. Feel free to stick a help-wanted label on this and leave it for the community to add. I was mostly filing an issue for visibility before tinkering. I'll...