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 | brett.cannon |
|---|---|
| Recipients | Rhamphoryncus, brett.cannon, ggenellina, gpk, jamescooper, thomasda, yangzhang |
| Date | 2008年02月05日.22:57:52 |
| SpamBayes Score | 0.24490608 |
| Marked as misclassified | No |
| Message-id | <1202252273.95.0.0074960983569.issue1722344@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hold on, why is that wrong? What if the threads block forever, preventing shutdown? sys.exit() is not exactly some namby-pamby function but a forced shutdown of the interpreter that should guarantee that the interpreter quits. Changing its semantics now would take that away. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月05日 22:57:54 | brett.cannon | set | spambayes_score: 0.244906 -> 0.24490608 recipients: + brett.cannon, gpk, ggenellina, Rhamphoryncus, yangzhang, thomasda, jamescooper |
| 2008年02月05日 22:57:53 | brett.cannon | set | spambayes_score: 0.244906 -> 0.244906 messageid: <1202252273.95.0.0074960983569.issue1722344@psf.upfronthosting.co.za> |
| 2008年02月05日 22:57:52 | brett.cannon | link | issue1722344 messages |
| 2008年02月05日 22:57:52 | brett.cannon | create | |