#10354: encoding.force_unicode exception unclear/vague, update to clarify
exception
-------------------------------------+--------------------------------------
Reporter: monkut | Owner: nobody
Status: closed | Milestone:
Component: Core framework | Version: 1.0
Resolution: wontfix | Keywords: exception-clarification
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by jacob):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
The problem with this technique is that it overrides the original
traceback, leaving you no way of accessing the original traceback object.
That's bad form for a number of reasons, the biggest being this: what if
the body `__unicode__` method itself raises a `TypeError`? You'd loose
that original exception, and be mistaken into thinking it was a returning-
the-wrong-type issue.
--
Ticket URL: <http://code.djangoproject.com/ticket/10354#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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
