Alexander Belopolsky added the comment: >> I want people to standardize on status=1 for a generic failure code.
> Why that? Multiple error codes can be used by the same program, depending on > the kind of error. Antoine, please read what I write carefully before disagreeing. I want "to standardize on status=1 for a **generic** failure code". Cooperating processes can certainly agree on other values for the specific failure modes. What I really want to avoid is the use of -1 as a generic failure code, because it leads to a rather common error rc = subprocess.call(..) if rc < 0: raise Error # never reached! ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24053> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com