Changes between Initial Version and Version 1 of Ticket #5640
- Timestamp:
- Sep 29, 2007, 7:55:15 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5640
- Property Has patch unset
- Property Owner changed from to
- Property Triage Stage Unreviewed → Design decision needed
- Property Summary utils.encoding.force_unicode should never throw UnicodeDecodeError → Request to improve error handling in utils.encoding.force_unicode.
-
Ticket #5640 – Description
initial v1 1 1 migrating a large django project to trunk version > 5609 (i.e. after Unicode branch was merged) can be very painful due to a bug(?!) in utils.encoding.force_unicode 2 2 3 basically, following the instructions here http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist is the right thing to do, but it is very difficult in a larger project to catch all the strings that might need and u''before them.3 basically, following the instructions here http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist is the right thing to do, but it is very difficult in a larger project to catch all the strings that might need and {{{u''}}} before them. 4 4 5 5 Make the slightest oversight, and you lose the ability to debug your models/views/templates as utils.encoding.force_unicode will throw an UnicodeDecodeError exception like this one: