Message331714
| Author |
edmundselliot@gmail.com |
| Recipients |
belopolsky, berker.peksag, edmundselliot@gmail.com, mark.dickinson, martin.panter, pitrou, rbcollins, scoder, serhiy.storchaka, skrah, terry.reedy |
| Date |
2018年12月12日.18:58:48 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1544641128.34.0.788709270274.issue24053@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I have personally come across situations where I am calling a Python script from a C program and would like to check the exit codes of the script, and have had to write sys.exit(1) and sys.exit(0) in Python, and compared them to EXIT_SUCCESS/EXIT_FAILURE in C. It would have been easy to introduce a bug where I returned the wrong exit code, so I was hoping they would have been implemented in sys.
It seems like a no-brainer to add these, they reduce magic number use and improve the accessibility of Python to people coming from C. I would love to add these if everyone is OK with it. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2018年12月12日 18:58:48 | edmundselliot@gmail.com | set | recipients:
+ edmundselliot@gmail.com, terry.reedy, mark.dickinson, belopolsky, pitrou, scoder, rbcollins, skrah, berker.peksag, martin.panter, serhiy.storchaka |
| 2018年12月12日 18:58:48 | edmundselliot@gmail.com | set | messageid: <1544641128.34.0.788709270274.issue24053@psf.upfronthosting.co.za> |
| 2018年12月12日 18:58:48 | edmundselliot@gmail.com | link | issue24053 messages |
| 2018年12月12日 18:58:48 | edmundselliot@gmail.com | create |
|