Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow control of local stdout/stderr #646

bitprophet opened this issue May 17, 2012 · 0 comments

Allow control of local stdout/stderr #646

bitprophet opened this issue May 17, 2012 · 0 comments


Copy link

@bitprophet bitprophet commented May 17, 2012

Feature request: even in pty=False, combine_stderr=False situations where we have access to both remote stdout/stderr, it's sometimes desirable to change what local streams those go to.

E.g. wanting to combine both stdout and stderr into local stdout, while still having access to distinct .stdout and .stderr results from the run() statement. (Otherwise, using combine_stderr would be the right solution.)

This can and probably should extend to allowing user control over what stream objects Fabric writes the remote streams to, in case they want to use their own eg StringIO objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.