[issue14966] Fully document subprocess.CalledProcessError

Andrew Svetlov added the comment: Documented in #15501. I like to close this issue as duplicate. If anybody don't agree with closing feel free to reopen this one. -- nosy: +asvetlov resolution: -> duplicate stage: -> committed/rejected status: open -> closed __

[issue14966] Fully document subprocess.CalledProcessError

Changes by Anton Barkovsky : -- nosy: +anton.barkovsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue14966] Fully document subprocess.CalledProcessError

Michael Driscoll added the comment: I don't see the error, TimeoutExpired, documented either. At least the doc page mentions CalledProcessError a couple times. Do we want to use the docstring for CalledProcessError for the documentation page? Where on the page would it go? I assume we'd want

[issue14966] Fully document subprocess.CalledProcessError

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue14966] Fully document subprocess.CalledProcessError

New submission from Nick Coghlan : CalledProcessError provides a nice encapsulation for a returncode, the original command and any partial output. The API should be officially documented so that third party subprocess.Popen convenience wrappers can use it easily. -- assignee: docs@pyth