#20530: Incorrect QUERY_STRING handling on Python 3
-----------------------------+-------------------------------------
Reporter: mitsuhiko | Owner: aaugustin
Type: Bug | Status: closed
Component: Core (URLs) | Version: 1.5
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"65b6eff322a4a3331601e111934dee95c090961c"]:
{{{
#!CommitTicketReference repository=""
revision="65b6eff322a4a3331601e111934dee95c090961c"
Fixed #20530 -- Properly decoded non-ASCII query strings on Python 3.
Thanks mitsuhiko for the report.
This commit just adds a test since the problem was fixed in 8aaca651.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20530#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.d887093b156699d64735fc3a174629be%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
