Change by Fangyi Zhou :
--
nosy: +fangyizhou
___
Python tracker
<https://bugs.python.org/issue5115>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Fangyi Zhou :
--
nosy: +fangyizhou
___
Python tracker
<https://bugs.python.org/issue26534>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fangyi Zhou added the comment:
I choose to implement the first way. I believe this is in favour in prevention
of resource leaks and zombie processes.
https://github.com/python/cpython/pull/5684
--
___
Python tracker
<https://bugs.python.
Change by Fangyi Zhou :
--
keywords: +patch
pull_requests: +5480
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32795>
___
___
Python-
Fangyi Zhou added the comment:
As far as I have discovered, the bash process is killed by after the timeout.
Presumably the pipe is still open due to the sleep process, so in order to
retrieve any output from stdout/stderr, the read waits on the pipe, hence
leading to timeout not respected
Fangyi Zhou added the comment:
I think the issue is that the process is not terminated.
If you increase the sleep duration, you would see that the sleep process is not
killed by SIGKILL.
--
nosy: +fangyizhou
___
Python tracker
<ht
Fangyi Zhou added the comment:
Hi. I've updated the docs.
I'm wondering if the code needs to be patched as well. Essentially we should
raise a unified Exception for unable to get the username I suppose?
Please let me know if you have any comments/suggestions on wordi
Change by Fangyi Zhou :
--
keywords: +patch
pull_requests: +5426
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Fangyi Zhou :
--
pull_requests: +5417
___
Python tracker
<https://bugs.python.org/issue30688>
___
___
Python-bugs-list mailing list
Unsubscribe: