By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,199 Members | 1,714 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,199 IT Pros & Developers. It's quick & easy.

worker thread catching exceptions and putting them in queue

P: n/a
All,

in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

considering that an exception is an object I feel it ought to be
possible, however I do not see how to go about it.

does anyone have a pointer towards the solution?

Paul
Mar 5 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Paul Sijben wrote:
All,

in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

considering that an exception is an object I feel it ought to be
possible, however I do not see how to go about it.

does anyone have a pointer towards the solution?

Just raise the exception object found in the queue. Only make sure it _is_
an exception, as you can raise everything. So in your queue-putting-code
you might consider discriminating between the two cases, like this:
while True:
try:
result = 1, work()
except:
result = 2, sys.exc_info()[1]
queue.put(result)

-------
while True:
kind, result = queue.get()
if kind == 1:
do(result)
elif kind == 2:
raise result
Diez
Mar 5 '07 #2

P: n/a
Paul Sijben schrieb:
All,

in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

considering that an exception is an object I feel it ought to be
possible, however I do not see how to go about it.

does anyone have a pointer towards the solution?

Paul
You're right, even exceptions are objects in Python. For further
studies, read http://docs.python.org/lib/module-exceptions.html

You can catch an exception like this:
try:
worker.do_some_work_that_may_raise_an_exception()
except Exception, e:
# the first argument is the type of error you want to handle
# it is Exception here, the baseclass of all computation exceptions
# the second argument is the variable (name) where you want to save
# the specific exception raised to
# it's 'e' here, a common shortcut for exception
exception_handler.handle(e)
# notice that you can pass e around as you like

For further information on exceptions and how to handle them, read
chapter 8 of the tutorial, especially starting from 8.3:
http://docs.python.org/tut/node10.ht...00000000000000

P.S. I don't know if what I told still applies to Python 3.0 -- a lot of
changes are upcoming related to exception raising and handling.
Mar 5 '07 #3

P: n/a
Stargaming & Diez,

thanks very much!

Stargaming wrote:
Paul Sijben schrieb:
>All,

in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

considering that an exception is an object I feel it ought to be
possible, however I do not see how to go about it.

does anyone have a pointer towards the solution?

Paul

You're right, even exceptions are objects in Python. For further
studies, read http://docs.python.org/lib/module-exceptions.html

You can catch an exception like this:
try:
worker.do_some_work_that_may_raise_an_exception()
except Exception, e:
# the first argument is the type of error you want to handle
# it is Exception here, the baseclass of all computation exceptions
# the second argument is the variable (name) where you want to save
# the specific exception raised to
# it's 'e' here, a common shortcut for exception
exception_handler.handle(e)
# notice that you can pass e around as you like

For further information on exceptions and how to handle them, read
chapter 8 of the tutorial, especially starting from 8.3:
http://docs.python.org/tut/node10.ht...00000000000000

P.S. I don't know if what I told still applies to Python 3.0 -- a lot of
changes are upcoming related to exception raising and handling.
Mar 6 '07 #4

P: n/a
In article <45*********************@news.xs4all.nl>,
Paul Sijben <pa*********@xs4all.nlwrote:
>
in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

considering that an exception is an object I feel it ought to be
possible, however I do not see how to go about it.
One caution: because exceptions keep stack frames alive, you can have
garbage collection problems. Make sure to del the exception when you're
done with it.
--
Aahz (aa**@pythoncraft.com) <* http://www.pythoncraft.com/

"I disrespectfully agree." --SJM
Mar 8 '07 #5

P: n/a
En Thu, 08 Mar 2007 13:31:14 -0300, Aahz <aa**@pythoncraft.comescribió:
In article <45*********************@news.xs4all.nl>,
Paul Sijben <pa*********@xs4all.nlwrote:
>>
in a worker thread setup that communicates via queues is it possible to
catch exceptions raised by the worker executed, put them in an object
and send them over the queue to another thread where the exception is
raised in that scope?

One caution: because exceptions keep stack frames alive, you can have
garbage collection problems. Make sure to del the exception when you're
done with it.
Note that it's the traceback who keeps stack frames alive, not the
exception itself (at least on the current Python versions, might change in
the future). If no fancy processing of the traceback is needed, maybe
converting it to string (using the traceback module) before posting it to
the queue is enough.

--
Gabriel Genellina

Mar 8 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.