On Sat, 09 Sep 2006 12:59:23 +0200, Gustavo Carneiro
<[EMAIL PROTECTED]> wrote:
> On 9/9/06, Jan Kanis <[EMAIL PROTECTED]> wrote:
>> However, PyGTKs problem does get
>> solved, as long as there is _a_ thread that returns to the interpreter
>> within some timefr
At the risk of waking up a thread that was already declared dead, but
perhaps this is usefull.
So, what happens is pythons signal handler sets a flag and registrers a
callback. Then the main thread should check the flag and make the callback
to actually do something with the signal. However
On Fri, 07 Jul 2006 01:25:19 +0200, Phillip J. Eby <[EMAIL PROTECTED]>
wrote:
>
>>> - or so it feels like to the person who's experiencing it.
>>
>> Have you ever been that person, or come across such a situation?
>
> Many times. The hard thing about trying to provide use cases for this
> is
On Thu, 06 Jul 2006 18:28:12 +0200, Phillip J. Eby <[EMAIL PROTECTED]>
wrote:
> Here's the reason I think this keeps coming up, and why Guido's "just
> use a class" argument doesn't really address the actual problem that's
> taking place.
I agree this argument is not generally applicable in
