Matthew Sherborne <[EMAIL PROTECTED]> writes:
>
> Thanks again. I didn't know about Queue.
>
Yeah, Queue.Queue rocks for multi-threading! :-)
--
Vennlig hilsen
Syver Enstad
___
ActivePython mailing list
[EMAIL PROTECTED]
To unsubscribe: http://
Thanks all, and special thanks to Jeff Shannon for pointing out the Queue
object.
I used the Queue. It's going good now. And I used the blocking get method,
so it has almost cpu usage when idle. :)
It was reading data from 4 serial ports (one on each thread) and the
consumer thread was pattern c
e
RuntimeError, "unexpected win32wait return value"
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Matthew SherborneSent: Wednesday, April 10, 2002 1:53
PMTo: [EMAIL PROTECTED]Subject:
Threading question
I'd like to do a
> Matthew Sherborne wrote:
>
> I'd like to do a "waitForMultipleObjects" but I can't find such a
> thing in python thread or threading modules.
If you're only on windows, you could use
win32event.waitForMultipleObjects, which is a simple wrapper around that
API call.
> I suppose I could use a s
[Matthew Sherborne wrote]
> Is this something that Python needs? Is it easy to implement for
> different platforms? Is it there, but I haven't noticed it?
>
> Any Ideas?
It is very possible that that functionality is not there. Whether this
is something that Python needs is probably better discu
I'd like to do a "waitForMultipleObjects" but I
can't find such a thing in python thread or threading modules.
I have one thread that loops waiting for any one of
four other threads to give him information, and of course the main thread may
notify him to stop looping and die.
So I've got
