<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 8/21/13 6:50 PM, Fábio Santos wrote:<br>
<blockquote
cite="mid:CAA=1kxRdo0ZAH_SLvZshFua7B4A=9YZ1H30KBi-KAGqDXiovVg@mail.gmail.com"
type="cite">
<p dir="ltr"><br>
On 21 Aug 2013 20:07, "Johannes Bauer" <<a
moz-do-not-send="true" href="mailto:dfnsonfsduifb@gmx.de">dfnsonfsduifb@gmx.de</a>>
wrote:<br>
><br>
> On 21.08.2013 11:11, Ulrich Eckhardt wrote:<br>
><br>
> > That said, there is never a need for deriving<br>
> > from the Thread class, you can also use it to run a
function without<br>
> > that. That way is IMHO clearer because the
threading.Thread instance is<br>
> > not the thread, just like a File instance is not a
file. Both just<br>
> > represent handles for manipulating the actual thing.<br>
><br>
> Huh? That I find most curious.<br>
><br>
> I *always* derive from threading.Thread and really like the
way that<br>
> thread setup works (instanciate Thread handle, call start).
Very<br>
> intuitive, never had the problems with clarity that you
mentioned. Could<br>
> you elaborate on your suggestion? I don't seem to quite get
it I'm afraid.<br>
><br>
> Best regards,<br>
> Johannes</p>
<p dir="ltr">I cannot tell whether you are trolling or are just
new to this, but you don't always have to use threads. You use
threads when you need multiple parts of your program running
concurrently. Don't inherit Thread if all you are doing is a
simple object with state, nor if your program does not need
concurrency.</p>
<br>
</blockquote>
I think it is safe to assume that Johannes meant, "when I use
threads, I never do it the way you suggested, I always derive from
threading.Thread."<br>
<br>
--Ned.<br>
<br>
</body>
</html>