Thanks Brian & Martin for the links.
I actually found another good one:
http://linuxgazette.net/107/pai.html
Cheers.
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, 16 Jun 2005 16:20:23 -0400, Peter Hansen wrote:
> Maxwell Hammer wrote:
>> This is related to an earlier post 'Help with thread related
>> tracebacks'...for which I have had no feedback yet :-(
>
> If the question was well formulated, and it's bee
Hi all,
This is related to an earlier post 'Help with thread related
tracebacks'...for which I have had no feedback yet :-(
How should a thread complete i.e. how should it exit?
Reading the python online docs one gets the idea that simply returning is
OK - but I'm not sure.
Is it ok to do a sys.e
Hope someone can help with a problem I'm having.
A python program I wrote terminates with the following traceback.
*** start traceback ***
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.4/atexit.py", line 22, in _run_exitfuncs
func(*targs, **kargs)
On Fri, 10 Jun 2005 04:52:12 -0700, wooks wrote:
>
> Your understanding of Usenet is that a post has to "appeal" (for the
> want of a better word) to the majority of the NG readership.
>
> Look over a hundred people took a look (and the hits are steadily
> going up whether despite or because of
On Sat, 19 Mar 2005 22:35:39 -0500, Peter Hansen wrote:
> When you say "only one thread running", did you mean only
> one monitor thread in addition to the main thread, or did
> you really mean only the main thread was active at this time?
I meant there was the main app and one thread. The proble
An application I am developing executes many threads and then has a
"monitor" part that waits for certain events. One of these events causes
the application to have to shutdown. On shutdown the monitor part
notifies the threads of a shutdown, and the threads must cleanup and exit.
When all threads
