Skip to content
This repository

ipython 0.11 buffers external command output till the cmd is done #978

Closed
rxwen opened this Issue November 07, 2011 · 3 comments

3 participants

rxwen Fernando Perez Min RK
rxwen

I run some command within ipython on a windows xp host. These commands take some time to finish.
The output of these command weren't shown until all commands finished running. The behavior is totally different from previous version, which output are printed immediately.

For instance, input "!netstat -p tcp -b -o -a -n 1" command which runs infinitely, the output will never be seen.

rxwen

When I did similar thing on a ubuntu host, everything worked fine. E.g., run "!top" command, the output can be seen immediately and refreshed fine.

Min RK
Owner

Yes, this is Windows specific.

Do:

ip = get_ipython()
ip.system = ip.system_raw

To switch back to using os.system for ! escapes. I think this will go back to being the default behavior in 0.12, because nobody seems to be able to remember why we kept it that way on Windows.

Min RK minrk referenced this issue from a commit in minrk/ipython November 08, 2011
Min RK use system_raw in terminal, even on Windows
`system_raw` uses `os.system` instead of `utils.process.system`, and makes
more sense in a Terminal session.

There was discussion that it should be otherwise on Windows, but I can't
find any actual evidence for why this would be the case, and there are very
clear disadvantages to not using `os.system` (see #978 and #181).

closes gh-978
a7b4809
Fernando Perez
Owner

@minrk, I'm closing this one since the PR for it went in. @rxwen, please reopen if you still see a problem.

Fernando Perez fperez closed this November 11, 2011
Brian E. Granger ellisonbg referenced this issue from a commit January 10, 2012
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.