Your interpreter is buffering. Add a call to sys.stdout.flush() after your print statement.
More Related Contents:
- link several Popen commands with pipes
- How to use `subprocess` command with pipes
- Retrieving the output of subprocess.call() [duplicate]
- Python subprocess/Popen with a modified environment
- Subprocess.Popen: cloning stdout and stderr both to terminal and variables
- live output from subprocess command
- Popen waiting for child process even when the immediate child has terminated
- Python popen command. Wait until the command is finished
- How can I specify working directory for popen
- Multiple pipes in subprocess
- File not found error when launching a subprocess containing piped commands
- subprocess readline hangs waiting for EOF
- Popen with conflicting executable/path
- How do I get ‘real-time’ information back from a subprocess.Popen in python (2.5)
- subprocess.Popen() error (No such file or directory) when calling command with arguments as a string
- How to write to stdout AND to log file simultaneously with Popen?
- Keep a subprocess alive and keep giving it commands? Python
- Launch a shell command with in a python script, wait for the termination and return to the script
- Python subprocess: how to use pipes thrice? [duplicate]
- What’s the difference between subprocess Popen and call (how can I use them)?
- Communicate multiple times with a process without breaking the pipe?
- How do I eliminate Windows consoles from spawned processes in Python (2.7)? [duplicate]
- Python – how to execute shell commands with pipe, but without ‘shell=True’?
- Bash style process substitution with Python’s Popen
- Why does subprocess.Popen() with shell=True work differently on Linux vs Windows?
- How to do multiple arguments with Python Popen?
- subprocess.wait() not waiting for Popen process to finish (when using threads)?
- Opening a process with Popen and getting the PID
- subprocess.Popen in different console
- What is the subprocess.Popen max length of the args parameter?