Message153940
| Author |
tarek |
| Recipients |
grahamd, neologix, pitrou, tarek |
| Date |
2012年02月22日.09:20:26 |
| SpamBayes Score |
8.02865e-08 |
| Marked as misclassified |
No |
| Message-id |
<1329902428.03.0.644805847911.issue14073@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Mmm.. you did not say yet why you are against this feature, other than "the lib *should not* use non-daemonized threads"
This sounds like "the lib should not use feature X in Python because it will block everything"
And now we're proposing to remove the limitation and you are telling me I am vague and unreasonable.
Let me try differently then.
Consider this script to be a library I don't control. I need to call the .stop() function when my main application shuts down.
I can't use signals because you forbid it in mod_wsgi
How do I do, since asking the person to daemonize his thread is not an option ?
I see several options:
1 - monkey patch the lib
2 - remove regular threads from Python, or making them always daemonized
3 - add an atexit() option in threads in Python
4 - use signals and drop the usage of mod_wsgi
I think 3- is the cleanest. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年02月22日 09:20:28 | tarek | set | recipients:
+ tarek, pitrou, grahamd, neologix |
| 2012年02月22日 09:20:28 | tarek | set | messageid: <1329902428.03.0.644805847911.issue14073@psf.upfronthosting.co.za> |
| 2012年02月22日 09:20:27 | tarek | link | issue14073 messages |
| 2012年02月22日 09:20:26 | tarek | create |
|