#12151: UnicodeEncodeError from django.contrib.comments.views.utils line 41.
----------------------------------------------+-----------------------------
Reporter: mikl | Owner: nobody
Status: closed | Milestone: 1.2
Component: django.contrib.comments | Version: SVN
Resolution: fixed | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------------+-----------------------------
Changes (by kmtracey):
* status: reopened => closed
* resolution: => fixed
Comment:
The reported problem here has been fixed. The failure case posted to
#11716 pointed out a different place where the comments code needed to
deal with invalid PK data submitted to it, and that has been done in
r12800/r12801. It doesn't appear to be all that easy to cause a
!ValidationError to be raised in the place identified here, since the
model involved here is the comments model itself, not the model comments
are being attached to. You'd need to have a comments model with a non-
autofield PK, I think. I don't even know if that is feasible. If it is, it
deserves its own ticket, as it's a bit more of a complex situation than
the relatively simple case of invalid submitted data covered by this
ticket.
--
Ticket URL: <http://code.djangoproject.com/ticket/12151#comment:14>
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 django-upda...@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.
