[issue4684] sys.exit() exits program when non-daemonic threads are still running

Changes by Thomas Wouters : -- resolution: -> fixed status: open -> closed superseder: -> Thread shutdown exception in Thread.notify() ___ Python tracker ___ ___

[issue4684] sys.exit() exits program when non-daemonic threads are still running

Joseph Malicki added the comment: Is it actually just documentation? Before Python 2.5, things worked according to the documentation, and nothing in the revisions that changed the behavior suggested this change in behavior was intentional. Moving the WaitForThreadShutdown() from Modules/main.c

[issue4684] sys.exit() exits program when non-daemonic threads are still running

R. David Murray added the comment: Attached is a version of your program that calls sys.exit from a thread other than the main one. That sys.exit does not cause python to shut down. Exiting the main program by "falling off the end" does not result in Python shutdown (pass an arbitrary argument

[issue4684] sys.exit() exits program when non-daemonic threads are still running

Joseph Malicki added the comment: It seems like this was introduced by the fix for Issue 1566280. Note that the threading module docs clear state: "A thread can be flagged as a “daemon thread”. The significance of this flag is that the entire Python program exits when only daemon threads are l

[issue4684] sys.exit() exits program when non-daemonic threads are still running

New submission from Mark Florisson : sys.exit() exits the program when non-daemonic threads are still running, in versions >= 2.5. Test included. A demonstration here: http://paste.pocoo.org/show/95766/ (On debian GNU/Linux) -- components: None files: foo.py messages: 77978 nosy: eggy