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 rbcollins
Recipients belopolsky, berker.peksag, mark.dickinson, martin.panter, pitrou, rbcollins, scoder, serhiy.storchaka, skrah, terry.reedy
Date 2015-11-27.18:15:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
@Serhiy, EXIT_FAILURE is used in Python's C code itself (just once admittedly, and then we use 0 sometimes for success and sometimes for errors, and then 1 for errors... aiee.)

FWIW to the extent that folk want to write posix code in Python, I'm all for helping them, I find the amount of help this will be to be hard to assess. There is some code to adding the constants in documentation and learning surface area.

Right now we don't document all the ways Python can interact with exit codes, and I suspect thats actually a bigger burden than writing the code to generate any given code.
Date User Action Args
2015-11-27 18:15:59rbcollinssetrecipients: + rbcollins, terry.reedy, mark.dickinson, belopolsky, pitrou, scoder, skrah, berker.peksag, martin.panter, serhiy.storchaka
2015-11-27 18:15:58rbcollinssetmessageid: <>
2015-11-27 18:15:58rbcollinslinkissue24053 messages
2015-11-27 18:15:58rbcollinscreate