pty behavior (& tests) fail on Linux & headless about invoke HOT 3 CLOSED

Googled a bit more to check the above link's assertion that one needs to explicitly tell pexpect to expect an EOF, and as it turns out one of the official pexpect homepages mentions this! Go here: http://www.noah.org/python/pexpect/ and search for 'exception'.

Will poke at this side of things and hope it meshes with how I am using the lib...

from invoke.

Bugger, with p.expect(pexpect.EOF) in place, the error does not fire, but it seems to be skipping the out_filter attached to interact(). I think this is because expect means to wait until its arg shows up [duh] and thus by the time we arrive at our interact call things are already done.

The docs mention how when you expect-til-EOF, the output is available in p.before, and that bears up -- when expecting, it contains the stdout/err mix, when not expecting, it's None. However this doesn't help me because I need realtime.

Need to figure out if there's another way or if I should just suck it up and try catching this specific OSError and move on.

from invoke.

Nope, no real way around this. Sucking up & catching/ignoring this specific OSError, and also attaching to result object for sanity's sake. Seriously doubt anybody will need it, but now my conscience is clean.

from invoke.