Hey everyone,
In some cases, it seems as though wxProcess isn't capturing stderr.
If one modifies the Process.py demo to also get the error stream and
read, then running the demo compare:
sh
to
python -u -c "import code;code.interact()"
The python prompt is sent to stderr, and it is displayed with the
modified Process.py (though due to reading semantics may come in a
strange order). However, sh never prints its prompt. I've tried
working around this limitation via stderr redirection and os.execl with
crazy things like:
python -c "import os;os.execl('/bin/sh/', '/bin/sh')" 2>&1
... but this hasn't helped so far. I've also tried bash, but it seems
to have the same issue.
Anyone have any ideas?
- Josiah
Nevermind, I just needed to use the right incantation to tell sh not to
use gnu readline (--noediting).
···
Josiah Carlson <jcarlson@uci.edu> wrote:
Hey everyone,
In some cases, it seems as though wxProcess isn't capturing stderr.
If one modifies the Process.py demo to also get the error stream and
read, then running the demo compare:
sh
to
python -u -c "import code;code.interact()"
The python prompt is sent to stderr, and it is displayed with the
modified Process.py (though due to reading semantics may come in a
strange order). However, sh never prints its prompt. I've tried
working around this limitation via stderr redirection and os.execl with
crazy things like:
python -c "import os;os.execl('/bin/sh/', '/bin/sh')" 2>&1
... but this hasn't helped so far. I've also tried bash, but it seems
to have the same issue.
Anyone have any ideas?
- Josiah
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org