#14035: Cannot access POST after request.encoding was set to a custom value
------------------------------------+---------------------------------------
Reporter: zimnyx | Owner: nobody
Status: reopened | Milestone:
Component: HTTP handling | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by russellm):
* status: closed => reopened
* resolution: wontfix =>
Comment:
I have triaged approx 40 tickets today. I need to triage another 120
before I can start work on fixing bugs in the 1.3 release. I hope you'll
understand that occasionally, human beings make errors when they're doing
labor intensive work. I hope you've also noted that if you explain
yourself clearly, human beings are usually willing to admit their mistakes
and move on.
On the other hand, human beings don't generally take too kindly to being
snarked at when they are volunteering their time to help out others. :-)
--
Ticket URL: <http://code.djangoproject.com/ticket/14035#comment:7>
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.
