Message 68559 - 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	Rhamphoryncus
Recipients	Rhamphoryncus, benjamin.peterson, gvanrossum, pitrou
Date	2008-06-22.07:04:56
SpamBayes Score	0.008284968
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
* cause/context cycles should be avoided. Naive traceback printing could become confused, and I can't think of any accidental way to provoke it (besides the problem mentioned here.) * I suspect PyErr_Display handled string exceptions in 2.x, and this is an artifact of that * No opinion on PyErr_DisplaySingle * PyErr_Display is used by PyErr_Print, and it must end up with no active exception. Additionally, third party code may depend on this semantic. Maybe PyErr_DisplayEx? * +1 on standardizing tracebacks

* cause/context cycles should be avoided.  Naive traceback printing
could become confused, and I can't think of any accidental way to
provoke it (besides the problem mentioned here.)

* I suspect PyErr_Display handled string exceptions in 2.x, and this is
an artifact of that

* No opinion on PyErr_DisplaySingle

* PyErr_Display is used by PyErr_Print, and it must end up with no
active exception.  Additionally, third party code may depend on this
semantic.  Maybe PyErr_DisplayEx?

* +1 on standardizing tracebacks

History
Date	User	Action	Args
2008-06-22 07:04:59	Rhamphoryncus	set	spambayes_score: 0.00828497 -> 0.008284968 recipients: + Rhamphoryncus, gvanrossum, pitrou, benjamin.peterson
2008-06-22 07:04:58	Rhamphoryncus	set	spambayes_score: 0.00828497 -> 0.00828497 messageid: <[email protected]>
2008-06-22 07:04:57	Rhamphoryncus	link	issue3112 messages
2008-06-22 07:04:56	Rhamphoryncus	create