Message156691
| Author |
pitrou |
| Recipients |
David.Manowitz, docs@python, ggenellina, jgehrcke, pitrou, stutzbach, terry.reedy |
| Date |
2012年03月24日.10:47:51 |
| SpamBayes Score |
0.00014367106 |
| Marked as misclassified |
No |
| Message-id |
<1332586072.39.0.983087451163.issue6634@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I don't see why this should be considered acceptable behavior. Why
> don't threads have their own ThreadExit exception, rather than
> overloading the use, and therefore, the meaning, of the SystemExit
> exception? As indicated by their names, sys.exit and the SystemExit
> exception should *only* be used to exit the entire system, not just a
> thread!
I agree the situation isn't optimal. However, fixing this would also break compatibility with any application that uses sys.exit() in a thread and expects it to exit the thread, not the whole process. So we're kind of stuck with it. |
|