This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dmacnet
Recipients dmacnet
Date 2016-05-31.16:35:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464712500.44.0.979958949461.issue27167@psf.upfronthosting.co.za>
In-reply-to
Content
If a command run by subprocess.check_call() exits because of a signal, e.g. SIGPIPE, Popen._handle_exitstatus() encodes the signal number as a negative return code. check_call() then raises that as a CalledProcessError, which describes it as "returned non-zero exit status -13". This is misleading and undocumented. 

CalledProcessError.__str__() should check if self.returncode is negative and if so return a string indicating that it was "signal 13", not "exit status -13". Better yet, it should include the descriptive name of the signal, e.g., SIGPIPE.

And, the documentation for the subprocess module should note that a signal is converted into a negative returncode.
History
Date User Action Args
2016-05-31 16:35:00dmacnetsetrecipients: + dmacnet
2016-05-31 16:35:00dmacnetsetmessageid: <1464712500.44.0.979958949461.issue27167@psf.upfronthosting.co.za>
2016-05-31 16:35:00dmacnetlinkissue27167 messages
2016-05-31 16:35:00dmacnetcreate