#9608: Broken model unicode methods can lead to bare exceptions
-------------------------------------+--------------------------------------
Reporter: kmtracey | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* component: Uncategorized => Core framework
* needs_tests: => 0
* needs_docs: => 0
Comment:
I wouldn't want to diguise this error too much, but you're right about
bullet-proofing the debug page. Making repr() immune to the problem sounds
like a good fix, since that will help with interactive debugging as well.
Catching unicode encode errors and replacing it with something like "[Bad
Unicode data]" would work for me.
--
Ticket URL: <http://code.djangoproject.com/ticket/9608#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
