Message 120302 - 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	rupole
Recipients	ajaksu2, jyasskin, lekma, pitrou, rupole, vstinner
Date	2010-11-03.02:32:46
SpamBayes Score	0.00031719037
Marked as misclassified	No
Message-id	<1288751568.61.0.284664596361.issue3605@psf.upfronthosting.co.za>
In-reply-to

Content
I know this has been closed, but I disagree with the fix. Py_FatalError is designed to give a clean exit with a readable error message when the state of the interpreter is known to be compromised. Calling any python functions or accessing any python internals is only likely to lead to more issues that obscure the original problems. IMO the PyErr_Occurred needs to be removed entirely.

I know this has been closed, but I disagree with the fix. Py_FatalError is designed to give a clean exit with a readable error message when the state of the interpreter is known to be compromised.  Calling *any* python functions or accessing *any* python internals is only likely to lead to more issues that obscure the original problems.  IMO the PyErr_Occurred needs to be removed entirely.

History
Date	User	Action	Args
2010-11-03 02:32:48	rupole	set	recipients: + rupole, pitrou, vstinner, ajaksu2, jyasskin, lekma
2010-11-03 02:32:48	rupole	set	messageid: <1288751568.61.0.284664596361.issue3605@psf.upfronthosting.co.za>
2010-11-03 02:32:47	rupole	link	issue3605 messages
2010-11-03 02:32:46	rupole	create