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


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

Re: thread.interrupt_main() behaviour

Started byIan Kelly <ian.g.kelly@gmail.com>
First post2014-07-01 11:47 -0600
Last post2014-07-01 11:47 -0600
Articles 1 — 1 participant

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: thread.interrupt_main() behaviour Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-01 11:47 -0600

#73799 — Re: thread.interrupt_main() behaviour

FromIan Kelly <ian.g.kelly@gmail.com>
Date2014-07-01 11:47 -0600
SubjectRe: thread.interrupt_main() behaviour
Message-ID<mailman.11379.1404236879.18130.python-list@python.org>
On Tue, Jul 1, 2014 at 3:45 AM, Skip Montanaro <skip@pobox.com> wrote:
> On Tue, Jul 1, 2014 at 3:58 AM, Piyush Verma <114piyush@gmail.com> wrote:
>>
>> Since two threads are running same method, I wanted to know which main thread will be interrupted in both case.
>
> I'm no threading expert, but a process can only have one main thread,
> the one you labeled "P". Threads T2 and Tt2 will both interrupt that
> thread.

Also, the threading model has no hierarchy as suggested by the
diagram.  All threads are equals (except the main thread, which is
slightly more equal than others).

[toc] | [standalone]


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


csiph-web