#15661: LogEntry objects have no unicode method
-------------------------------------+-------------------------------------
Reporter: Keryn | Owner: nobody
Knight <keryn@…> | Milestone:
Status: new | Version: SVN
Component: | Keywords: logentry unicode
django.contrib.admin | Has patch: 1
Resolution: | Needs tests: 1
Triage Stage: Accepted |
Needs documentation: 0 |
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------
Changes (by lukeplant):
* needs_docs: => 0
* needs_better_patch: => 1
* needs_tests: => 1
* stage: Unreviewed => Accepted
Comment:
Sounds reasonable. The patch can be very simply optimised - it currently
looks up 3 translations and throws 2 away. The easiest solution, if
slightly less elegant, is a simple if/elif statement.
This needs a simple test - just create a new `class LogEntryTests` in
tests/regressiontests/admin_util/tests.py, or somewhere else if you can
find a better place.
--
Ticket URL: <http://code.djangoproject.com/ticket/15661#comment:1>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.