#1201: query string parsing problem
---------------------------+------------------------------------------------
Reporter: Eric Moritz | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This is a real bug (in Python 2.3). We should be using our own version of
parse_qs for 2.3, as Eric suggests. The specific thing about the query
string he mentions is that it's not of the form "?name=value", it's just
"?name", which is still valid.
--
Ticket URL: <http://code.djangoproject.com/ticket/1201#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
