Message238034
| Author |
Dan Nawrocki |
| Recipients |
Dan Nawrocki |
| Date |
2015年03月13日.15:22:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1426260142.17.0.720553845147.issue23658@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
It seems that the fix for 13854 (http://bugs.python.org/issue13854) actually tried to solve 2 issues:
1. handle non-integer, non-string arg to SystemExit
2. use exit code of 0 when the arg was a string
The change involved for #2 seems to go against the documentation for sys.exit:
"...In particular, sys.exit("some error message") is a quick way to exit a program when an error occurs."
Indeed, python 2.7.5 appears to follow this behavior:
[me@localhost ~]$ python -c 'raise SystemExit("bye")'; echo $?
bye
1
Shouldn't the return code from a subprocess when using multiprocessing match the return code when called w/o the multiprocessing module? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年03月13日 15:22:22 | Dan Nawrocki | set | recipients:
+ Dan Nawrocki |
| 2015年03月13日 15:22:22 | Dan Nawrocki | set | messageid: <1426260142.17.0.720553845147.issue23658@psf.upfronthosting.co.za> |
| 2015年03月13日 15:22:22 | Dan Nawrocki | link | issue23658 messages |
| 2015年03月13日 15:22:21 | Dan Nawrocki | create |
|