Message 146447 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	petri.lehtinen
Recipients	Trundle, ezio.melotti, ncoghlan, petri.lehtinen, pitrou, python-dev
Date	2011-10-26.18:11:08
SpamBayes Score	8.1936224e-07
Marked as misclassified	No
Message-id	<1319652669.58.0.787797432261.issue13188@psf.upfronthosting.co.za>
In-reply-to

Content
It seems this cannot be achieved the same way in 2.7 as the traceback is not directly associated with the exception. However, if we're currently in an exception handler and sys.exc_info() corresponds to the exception passed to generator.throw(), we could use the current traceback. Would this approach be too complicated and not worth it?

It seems this cannot be achieved the same way in 2.7 as the traceback is not directly associated with the exception. However, if we're currently in an exception handler and sys.exc_info() corresponds to the exception passed to generator.throw(), we could use the current traceback. Would this approach be too complicated and not worth it?

History
Date	User	Action	Args
2011-10-26 18:11:09	petri.lehtinen	set	recipients: + petri.lehtinen, ncoghlan, pitrou, ezio.melotti, Trundle, python-dev
2011-10-26 18:11:09	petri.lehtinen	set	messageid: <1319652669.58.0.787797432261.issue13188@psf.upfronthosting.co.za>
2011-10-26 18:11:09	petri.lehtinen	link	issue13188 messages
2011-10-26 18:11:08	petri.lehtinen	create