[issue27167] subprocess reports signal as negative exit status, not documented

Changes by Gregory P. Smith : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue27167] subprocess reports signal as negative exit status, not documented

Roundup Robot added the comment: New changeset 365b5e6163a6 by Gregory P. Smith in branch 'default': signal, socket, and ssl module IntEnum constant name lookups now return a https://hg.python.org/cpython/rev/365b5e6163a6 -- ___ Python tracker

[issue27167] subprocess reports signal as negative exit status, not documented

Changes by Gregory P. Smith : -- versions: -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue27167] subprocess reports signal as negative exit status, not documented

Gregory P. Smith added the comment: So this is mostly done... one oddity which may warrant improvement though: signal numbers have multiple names. ie: SIGABRT is also known as SIGIOT, etc. This is likely to be confusing to if the error message is surfaced to the user as most users only know o

[issue27167] subprocess reports signal as negative exit status, not documented

Roundup Robot added the comment: New changeset 1022d09d11e5 by Gregory P. Smith in branch 'default': issue27167: make the test not care about the exact signal name in the https://hg.python.org/cpython/rev/1022d09d11e5 -- ___ Python tracker

[issue27167] subprocess reports signal as negative exit status, not documented

Roundup Robot added the comment: New changeset f2d13349ea5d by Gregory P. Smith in branch 'default': Issue #27167: Clarify the subprocess.CalledProcessError error message text https://hg.python.org/cpython/rev/f2d13349ea5d -- nosy: +python-dev ___ Pyt

[issue27167] subprocess reports signal as negative exit status, not documented

Gregory P. Smith added the comment: docs updated (7b12180481da and 19d77132f38d). working on the error message update. -- ___ Python tracker ___

[issue27167] subprocess reports signal as negative exit status, not documented

Gregory P. Smith added the comment: I'll take this as a documentation update for 3.5 and a feature request for better message text in 3.6. -- assignee: -> gregory.p.smith nosy: +gregory.p.smith versions: +Python 3.6 ___ Python tracker

[issue27167] subprocess reports signal as negative exit status, not documented

New submission from David MacKenzie: 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-z