[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Terry J. Reedy added the comment: Please suggest a specific doc change at a specific location. IE, how *should* they read, not just what is wrong. -- assignee: georg.brandl -> d...@python nosy: +d...@python, tjreedy -georg.brandl stage: -> needs patch versions: +Python 3.2 -Python 2.4,

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Jan-Philip Gehrcke added the comment: Sorry for the delay. Before suggesting a doc change to correct/complete the description of the *current* situation, we actually should consider changing this situation. I think this is reasonable and I feel encouraged by Gabriel Genellina: > I see no rea

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Terry J. Reedy added the comment: I do not use threads so I cannot comment on the technical issue. Since the current behavior is not clearly a bug, I do not think a change would or know that it should be applied to 2.7/3.1. So I suggest that you both 1. Suggest a doc patch on this issue. That

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Changes by Daniel Stutzbach : -- nosy: +stutzbach ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

David Manowitz added the comment: 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 Sys

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Antoine Pitrou added the comment: > 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 th

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

David Manowitz added the comment: I have a couple of issues with that argument: 1.) Until fairly recently, the fact that sys.exit() when called from a non-primary thread only causes the thread to die, was not clearly documented (and still isn't in the python2.6 docs). Admittedly, thread.exit()

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

New submission from Jan-Philip Gehrcke : Hey there, hopefully I fill out this form in an adequate way! I ran into some problems while using sys.exit('msg') together with threads, which could have been avoided with slightly more information in the docs here: http://docs.python.org/library/sys.ht

[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour

Gabriel Genellina added the comment: I agree with you; the docs should be improved, and I see no reason for sys.exit("msg") NOT to write to stderr inside a child thread. -- nosy: +gagenellina ___ Python tracker __