Aahz wrote:
You can also use os._exit().
Yes! It works cleanly! Thanks a million!
OTOH, if I use sys.exit(), it's just hanging there.
Regards,
mk
--
http://mail.python.org/mailman/listinfo/python-list
Aahz wrote:
You can also use os._exit().
Thanks!
--
http://mail.python.org/mailman/listinfo/python-list
Stephen Hansen wrote:
I use threads all the time (well, for certain types of workloads) and
have never seen this.
Are your threads daemon threads? The only time I've seen sys.exit() not
close out my program is when I'm launching non-daemon threads on accident.
The snag is that my program is
On Feb 11, 2010, at 11:43 AM, Aahz wrote:
> In article ,
> mk wrote:
>>
>> I have a problem with a threaded program: it frequently hangs on sys.exit.
>>
>> The problem is that my program uses threads which in turn use paramiko
>> library, which itself is threaded.
>>
>> I try to gracefully
In article ,
mk wrote:
>
>I have a problem with a threaded program: it frequently hangs on sys.exit.
>
>The problem is that my program uses threads which in turn use paramiko
>library, which itself is threaded.
>
>I try to gracefully close the threads (below), but it doesn't always
>work, if pa
On Fri, Feb 5, 2010 at 7:25 AM, mk wrote:
> Hello everyone,
>
> I have a problem with a threaded program: it frequently hangs on sys.exit.
>
I use threads all the time (well, for certain types of workloads) and have
never seen this.
Are your threads daemon threads? The only time I've seen sys.e
