[issue10444] A mechanism is needed to override waiting for Python threads to finish

Emanuel Barry added the comment: Let's just close this. -- nosy: +ebarry resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Michael Hughes added the comment: Given that this is from five years ago, and I've moved on, I honestly can't say I care too deeply about this. My use case was for handling threads: * created by inexperienced python programmers that don't know about daemons * using third party python scripts

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Julien Palard added the comment: If nobody has nothing to add on this issue, I think it just should be closed. -- ___ Python tracker ___

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Julien added the comment: `daemon` flag cannot be changed after thread is started, the documentation is right and the code of the daemon setter is actually: if self._started.is_set(): raise RuntimeError("cannot set daemon status of active thread") But still it looks like a code

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Florent Xicluna florent.xicl...@gmail.com added the comment: Antoine wrote: You could instead enumerate() all threads and set their daemon flag to False, before shutting down the interpreter. If it is intended to work this way, it should be mentioned in the documentation. Currently the

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Changes by Skip Montanaro s...@pobox.com: -- nosy: -skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10444 ___ ___ Python-bugs-list

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Michael Hughes michaelahug...@gmail.com added the comment: Hey guys We don't always have control over all of the threads launched within our application. We might have inexperienced users writing basic scripts using threads, but they don't know enough about setting them to Daemon. Previous

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Antoine Pitrou pit...@free.fr added the comment: This looks like an ugly hack to solve a slightly exotic problem. You could instead enumerate() all threads and set their daemon flag to False, before shutting down the interpreter. -- nosy: +pitrou

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10444 ___

[issue10444] A mechanism is needed to override waiting for Python threads to finish

New submission from Michael Hughes michaelahug...@gmail.com: We use the Python interpreter embedded in our application, and would prefer to not block an exit of our application waiting for non-daemon threads to finish. I would like a mechanism exposed that queries for whether or not to wait.

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Michael Hughes michaelahug...@gmail.com added the comment: I have a patch here. It is to allow for a callback to be set on the main thread which gets called when there are non-daemon threads still alive on exit. The callback returns True or False indicating whether or not it wants to block. By

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Changes by Michael Hughes michaelahug...@gmail.com: Removed file: http://bugs.python.org/file19625/threadingchange.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10444 ___

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Michael Hughes michaelahug...@gmail.com added the comment: Scratch that last patch. It was missing part of the fix. I've removed the old patch now, and submitted the proper one. -- Added file: http://bugs.python.org/file19626/real.patch ___ Python

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Amaury Forgeot d'Arc amaur...@gmail.com added the comment: How do you use it? -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10444 ___

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Michael Hughes michaelahug...@gmail.com added the comment: To use the callback, you can do this: import threading def threadendcallback(): # return False to indicate that we don't # want to wait for any threads before exiting return False

[issue10444] A mechanism is needed to override waiting for Python threads to finish

Skip Montanaro s...@pobox.com added the comment: Why is setting your threads as daemons not an option? -- nosy: +skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10444 ___