Changes between Initial Version and Version 2 of Ticket #13583


Ignore:
Timestamp:
06/06/2010 09:15:54 PM (5 years ago)
Author:
kmtracey
Comment:

There is not enough information here to figure out what's going on....the error message output where? In a template, the snippet provided does produce correct output by default (for example if {{ form }} is used in the template for display). I suspect the observed problem is due to some incorrect way of outputting the error information in the template, or, if the "output" being referred to is some debugging information, then a misunderstanding about how Python displays unicode string representations (as phxx notes), not a bug in Django. A better place to ask for help in either case would be django-users.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13583

    • Property Status changed from new to closed
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Needs documentation unset
    • Property Resolution changed from to invalid
  • Ticket #13583 – Description

    initial v2  
    11If I use this construction:
    2 
     2{{{
    33forms.IntegerField(min_value=1, max_value=5,                                   
    44                                 error_messages = {
    55                                    'max_value': u'Ошибка!',
    66                                 })
    7 
     7}}}
    88The error message output is
    99u'u041e\u0448\u0438\u0431\u043a\u0430!'
Back to Top