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


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

Re: Bi-directional sub-process communication

Started byCameron Simpson <cs@zip.com.au>
First post2015-11-25 08:06 +1100
Last post2015-11-25 08:06 +1100
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: Bi-directional sub-process communication Cameron Simpson <cs@zip.com.au> - 2015-11-25 08:06 +1100

#99398 — Re: Bi-directional sub-process communication

FromCameron Simpson <cs@zip.com.au>
Date2015-11-25 08:06 +1100
SubjectRe: Bi-directional sub-process communication
Message-ID<mailman.36.1448400355.20593.python-list@python.org>
On 24Nov2015 06:33, israel <israel@eraalaska.net> wrote:
>On 11/23/2015 20:29, Cameron Simpson wrote:
>>On 24Nov2015 16:25, Cameron Simpson <cs@zip.com.au> wrote:
>>>Completely untested example code:
>>>
>>>class ReturnEvent:
>>>  def __init__(self):
>>>    self.event = Event()
>>
>>With, of course:
>>
>>   def wait(self):
>>     return self.event.wait()
>
>Of course :-) Ah, the Event() object comes from the threading module. 
>That makes sense. This should work perfectly. Thanks so much for 
>taking the time to help me out!

Glad to be of service,
Cameron Simpson <cs@zip.com.au>

All the doors in this ship have nice sunny dispositions. It is their pleasure 
to open for you, and their satisfaction to close with the knowledge of a job 
well done.     - Marvin _The Hitchhiker's Guide to the Galaxy_

[toc] | [standalone]


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


csiph-web