#15938: USE_THOUSAND_SEPARATOR breaks prepopulated_fields functionality
-------------------------------------+-------------------------------------
Reporter: lev.maximov@… | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
USE_THOUSAND_SEPARATOR | Needs documentation: 0
prepopulated_fields | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
I tried to look for override_settings documentation but I didn't find
enough. Is it correct the use of it as follows?
{{{
@override_settings(USE_THOUSAND_SEPARATOR = True, USE_L10N = True)
def test_prepopulated_maxlength_localized(self):
"""
Regression test for #15938: if USE_THOUSAND_SEPARATOR is set, make
sure
that maxLength (in the javascript) is rendered without separators.
"""
response =
self.client.get('/test_admin/admin/admin_views/prepopulatedpostlargeslug/add/')
self.assertContains(response, "maxLength: 1000") # instead of
1,000
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15938#comment:8>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
