#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
-----------------------------+-------------------------------------

Comment (by Aymeric Augustin <aymeric.augustin@…>):

 In [changeset:"7fcd6aa6695b39370154d6993cdbb3ba4363de91"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fcd6aa6695b39370154d6993cdbb3ba4363de91"
 [1.6.x] Fixed #20530 -- Properly decoded non-ASCII query strings on Python
 3.

 Thanks mitsuhiko for the report.

 Backport of 65b6eff3 and adaptation of 8aaca65 from master.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20530#comment:6>
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.43f3e8daef48b543867cd7bfb9c6f6ab%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to