Message 56338 - 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	ishimoto
Recipients	gvanrossum, ishimoto, lemburg, loewis, nnorwitz
Date	2007-10-11.06:04:20
SpamBayes Score	0.003775134
Marked as misclassified	No
Message-id	<1192082667.16.0.92558818847.issue1031213@psf.upfronthosting.co.za>
In-reply-to

Content
Sorry for insufficient comment. When a codec raised an exception, I think the exception should be reported. Otherwise, user cannot know why Python prints broken line of code. Should we silently clear the exception raised by codecs, or print a message such as "Codec raised an exception while processing compile error." ?

Sorry for insufficient comment.

When a codec raised an exception, I think the exception should be 
reported. Otherwise, user cannot know why Python prints broken line
of code.  

Should we silently clear the exception raised by codecs, or print a
message such as "Codec raised an exception while processing compile
error." ?

History
Date	User	Action	Args
2007-10-11 06:04:27	ishimoto	set	spambayes_score: 0.00377513 -> 0.003775134 recipients: + ishimoto, lemburg, gvanrossum, loewis, nnorwitz
2007-10-11 06:04:27	ishimoto	set	spambayes_score: 0.00377513 -> 0.00377513 messageid: <1192082667.16.0.92558818847.issue1031213@psf.upfronthosting.co.za>
2007-10-11 06:04:27	ishimoto	link	issue1031213 messages
2007-10-11 06:04:26	ishimoto	create