Say I want to run

sed

on a file. Is there anyway to put the contents of the file directly on the stdin of the Process object? Or do I need to actually use a shell so I can use

<

to redirect it from a file I put in the

input_digest

?

Yep

If I were to submit a PR to expose stdin would you be open to it? It'll be a good learning opportunity for me.

How would this work? You'd pass

bytes

into

Process

on the Python side, and the engine would feed those bytes into the process when it executes?

Yeah, same thing that happens with stdout/stderr but in reverse.

I think that could make sense, if you want to take a swipe at it

Yeah, I found at least some of it. I'll have to start playing with it to find the rest.

Why not

cat

though, as in the example I sent?

Cat isn't really needed as I can just use < on the command line. But it's more of a UI thing. If I give users arbitrary shell command line they're going to be able to run anything, use aliases out of their .cshrc files, etc. If I just give them a library of specific commands with stdin and out wired up to files, it's very clear to them that they're in an isolated environment.

But why not just

sed <some arguments> path/to/file

?

Well, both. In this particular case it literally is sed, but it's just one case of many, others that do require stdin

Gotcha