Duncan Booth wrote:
> Dale Strickland-Clark <[EMAIL PROTECTED]> wrote:
>
>> In Linux this is easy with 'signal' and 'kill' but how can I get one
>> Python process to signal another (possibly running as a service)?
>>
>> All I need is a simple prod with no other data being sent and none
>> being
Dale Strickland-Clark <[EMAIL PROTECTED]> wrote:
> In Linux this is easy with 'signal' and 'kill' but how can I get one
> Python process to signal another (possibly running as a service)?
>
> All I need is a simple prod with no other data being sent and none
> being returned - except that the si
Dennis Lee Bieber wrote:
> Unfortunately... You are on Windows...
>
> I think your choices become: Block, or Poll
>
> Check the Win32Api modules...
>
> win32event may be a candidate...
> CreateEvent()
> OpenEvent()
> PulseEvent()
> SetEvent()
> ResetEvent()
> WaitForSingleObject() or WaitForMul
Dale Strickland-Clark wrote:
> In Linux this is easy with 'signal' and 'kill' but how can I get one
> Python process to signal another (possibly running as a service)?
>
> All I need is a simple prod with no other data being sent and none being
> returned - except that the signal was delivered.
>
In Linux this is easy with 'signal' and 'kill' but how can I get one Python
process to signal another (possibly running as a service)?
All I need is a simple prod with no other data being sent and none being
returned - except that the signal was delivered.
Receiving a signal should generate an i
