Issue 1538556: PyThreadState_SetAsyncExc bug - Python tracker (original) (raw)

Issue1538556

Created on 2006-08-11 09:24 by gangesmaster, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg60968 - (view) Author: ganges master (gangesmaster) Date: 2006-08-11 09:24
while working on a library for raising exceptions in the context of another thread, i've come across a bug in PyThreadState_SetAsyncExc. if i raise an instance, sys.exc_info() confuses the exception value for the exception type, and the exception value is set None. if i raise the type itself, the interpreter creates an instance internally, but then i can't pass arguments to the exception. see this post for more info http://mail.python.org/pipermail/python-dev/2006-August/068158.html
msg84498 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-03-30 04:23
Is this still valid? I recall some discussions about raising exceptions in another thread and don't think the use case is supported.
msg85481 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-04-05 11:16
Agreed.
History
Date User Action Args
2022-04-11 14:56:19 admin set github: 43806
2009-04-05 11:16:53 georg.brandl set status: open -> closednosy: + georg.brandlmessages: + resolution: wont fix
2009-03-30 04:23:55 ajaksu2 set priority: normal -> lowtype: behaviorversions: + Python 2.6, - Python 2.5nosy: + ajaksu2messages: + stage: test needed
2006-08-11 09:24:51 gangesmaster create