Changes between Initial Version and Version 2 of Ticket #6272


Ignore:
Timestamp:
06/23/2008 01:39:17 PM (7 years ago)
Author:
ramiro
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6272

    • Property Patch needs improvement unset
    • Property Triage Stage changed from Unreviewed to Design decision needed
    • Property Needs tests unset
    • Property Needs documentation unset
  • Ticket #6272 – Description

    initial v2  
    1 The model fields defined in django.contrib.auth.models (and I assume other parts of django) use django.utils.translation.ugettext_lazy to specify the label (or another property from which the label is derived). The form field objects generated by form_for_* and ModelForm on these models return a django.utils.functional.__proxy__ object instead of a unicode object where ugettex_lazy is not used.
     1The model fields defined in django.contrib.auth.models (and I assume other parts of django) use django.utils.translation.ugettext_lazy to specify the label (or another property from which the label is derived). The form field objects generated by form_for_* and ModelForm on these models return a {{{django.utils.functional.__proxy__}}} object instead of a unicode object where ugettex_lazy is not used.
    22
    33I have a few helper template tags which are trying to alter the form field label with a concatenation, which is throwing an error for form_for_model and ModelForm forms for django.contrib.auth.models.User (and other django/contrib models that use ugettext_lazy).
    44
    5 As the documentation doesn't recommend or require the use of ugettext_lazy in it's examples and tutorials when defining models and forms, this inconsistent behaviour seems less than ideal. If django.utils.functional.__proxy__ could be changed with an __add__ (and other?) methods to behave more like a string/unicode object, that would be good?
     5As the documentation doesn't recommend or require the use of ugettext_lazy in it's examples and tutorials when defining models and forms, this inconsistent behaviour seems less than ideal. If {{{django.utils.functional.__proxy__}}} could be changed with an {{{__add__}}} (and other?) methods to behave more like a string/unicode object, that would be good?
    66
Back to Top