Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #38400 > unrolled thread

which situations should we use thread. join() ?

Back to article view | Back to comp.lang.python

Contents

  which situations should we use thread. join() ? iMath <redstone-cold@163.com> - 2013-02-07 20:32 -0800
    Re: which situations should we use thread. join() ? Chris Angelico <rosuav@gmail.com> - 2013-02-08 17:29 +1100
      Re: which situations should we use thread. join() ? Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com> - 2013-02-08 09:27 +0100

#38400 — which situations should we use thread. join() ?

which situations should we use thread. join() ?  
http://bpaste.net/show/yBDGfrlU7BDDpvEZEHmo/ 
 why do we not put thread. join() in this code ?  

[toc] | [next] | [standalone]

#38422

On Fri, Feb 8, 2013 at 3:32 PM, iMath <redstone-cold@163.com> wrote:
> which situations should we use thread. join() ?
> http://bpaste.net/show/yBDGfrlU7BDDpvEZEHmo/
>  why do we not put thread. join() in this code ?

I've no idea why you don't put thread.join() in that code. Maybe
because it isn't needed, maybe because someone likes to live on the
edge, maybe it's not so much "the edge" as positively cloud cuckoo
land. When should you use it? When you want to accomplish what the
function does, the details of which can be found in the Fine Manual.
Actually, you probably know already what it does, or you wouldn't even
be asking.

ChrisA

[toc] | [prev] | [next] | [standalone]

#38433

Am 08.02.2013 07:29, schrieb Chris Angelico:
> On Fri, Feb 8, 2013 at 3:32 PM, iMath <redstone-cold@163.com> wrote:
>> which situations should we use thread. join() ?
>> http://bpaste.net/show/yBDGfrlU7BDDpvEZEHmo/
>>   why do we not put thread. join() in this code ?
>
> I've no idea why you don't put thread.join() in that code. Maybe
> because it isn't needed, maybe because someone likes to live on the
> edge, maybe it's not so much "the edge" as positively cloud cuckoo
> land. When should you use it? When you want to accomplish what the
> function does, the details of which can be found in the Fine Manual.
> Actually, you probably know already what it does, or you wouldn't even
> be asking.

It isn't needed. I personally would prefer an explicit join(), but 
according to the documentation, "The entire Python program exits when no 
alive non-daemon threads are left.". In other words, the initial thread 
is not special and the interpreter will implicitly join() all non-daemon 
threads.

Which again makes me want to find out in what thread's context the 
atexit call is made...

Uli

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web