How to pipe input to python line by line from linux program?
I want to pipe the output of ps -ef to python line by line.
pipe
Multiprocessing – Pipe vs Queue
What are the fundamental differences between queues and pipes in Python’s multiprocessing package?
Checking for interactive shell in a Python script
I need to determine whether the shell which invoked my Python script was in interactive mode or not. If it was in interactive mode, the program should pipe output to less(1) for easy reading. If not, it should simply print its output to stdout, to allow it to be piped away to a printer, file, or a different pager.
Communicate multiple times with a process without breaking the pipe?
It’s not the first time I’m having this problem, and it’s really bugging me.
Whenever I open a pipe using the Python subprocess module, I can only communicate with it once, as the documentation specifies: Read data from stdout and stderr, until end-of-file is reached
Should I care about unnecessary cats?
A lot of command-line utilities can take their input either from a pipe or as a filename argument. For long shell scripts, I find starting the chain off with a cat makes it more readable, especially if the first command would need multi-line arguments.
What is the portable (POSIX) way to achieve process substitution?
Some shells, like bash, support Process Substitution which is a way to present process output as a file, like this:
zsh I/O redirection: redirecting and then piping; what is going on?
Can somebody explain what is going on in this command:
Why does the command shuf file > file leave an empty file, but similar commands do not?
3.1.1 Shell Operation
Using data read from a pipe instead than from a file in command options
Per man definition, this command gets the input from a file.
Why does process substitution result in a file called /dev/fd/63 which is a pipe?
I am trying to understand named pipes in the context of this particular example.