➜

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 gvanrossum
Recipients gvanrossum, ishimoto, lemburg, loewis, nnorwitz
Date 2007-10-11.16:53:28
SpamBayes Score 0.053762734
Marked as misclassified No
Message-id <ca471dc20710110950w657d321co1be40555a50e100b@mail.gmail.com>
In-reply-to <1192088669.94.0.457674661229.issue1031213@psf.upfronthosting.co.za>
Content 
There are tons of situations where such an exception will be
suppressed, ofr better or for worse. I don't think this one deserves
such a radical approach.

On 10/11/07, atsuo ishimoto <report@bugs.python.org> wrote:
>
> atsuo ishimoto added the comment:
>
> Codecs would hardly ever raises exception here.
> Usually, exception raised here would be a MemoryError. The unicode
> string we are trying to encode is just decoded by same codec. If codec
> raises exception other than MemoryError, the codec will likely have problem.
>
> I attached a script to print exception raised by codec. I wrote a "buggy"
> encoder, which never return string but raises an exception.
>
> _____________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1031213>
> _____________________________________
>
History
Date User Action Args
2007-10-11 16:53:28gvanrossumsetspambayes_score: 0.0537627 -> 0.053762734
recipients: + gvanrossum, lemburg, loewis, nnorwitz, ishimoto
2007-10-11 16:53:28gvanrossumlinkissue1031213 messages
2007-10-11 16:53:28gvanrossumcreate