Changes between Initial Version and Version 1 of Ticket #4472


Ignore:
Timestamp:
Jun 4, 2007, 2:48:03 AM (17 years ago)
Author:
Malcolm Tredinnick
Comment:

True. This is kind of obvious in retrospect. The __unicode__ method must return a unicode object, not anything else, so we cannot return lazy translation objects from those methods. Easy enough to fix; painful to track down if we're making the same error anywhere else, though.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4472

    • Property Keywords [unicode-branch] removed
    • Property Owner changed from Adrian Holovaty to Malcolm Tredinnick

  • Ticket #4472 – Description

    initial v1  
    1 smart_unicode and force_unciode throw TypeError exception when calling on instance of AnonymousUser. I got this error when trying something like this ( for model Articles.authors = ManyToManyField(User) ):
     1smart_unicode and force_unciode throw !TypeError exception when calling on instance of !AnonymousUser. I got this error when trying something like this ( for model {{{Articles.authors = ManyToManyField(User)}}} ):
    22{{{
    33from django.contrib.auth import AnonyousUser
    … …  
    66}}}
    77Then i got:
     8{{{
    89TypeError: coercing to Unicode: need string or buffer, __proxy__ found
    9 
     10}}}
    1011Full trackback is in attachment.
Back to Top