Fixed #6353 (again) by making force_unicode() and smart_str() a bit more robust
commit03ff5d4becc73fbb929fa37c5a2dc06e23dfb021
authormtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37>
Tue, 26 Aug 2008 18:53:51 +0000 (26 18:53 +0000)
committermtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37>
Tue, 26 Aug 2008 18:53:51 +0000 (26 18:53 +0000)
treeb2923bc5accdfb1945ae096d16bb80af396ff4de
parent5226b57f5e6a06bb169229261006d4c4e3791348
Fixed #6353 (again) by making force_unicode() and smart_str() a bit more robust
in the face of funky Exception instances. This is slightly symptomatic of
problems in the calling code, but we don't want to raise a secondary exception
whilst trying to display the first one. Based on a patch from Karen Tracey.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8588 bcc190cf-cafb-0310-a4f2-bffc1f526a37
django/utils/encoding.py