This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author luiz.poleto
Recipients luiz.poleto, orsenthil, r.david.murray, ruben.orduz
Date 2016-04-20.14:08:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAHFUrke1dFKBco3hxNDxNUUYgZob89dG15TtTdREKMwTXVE1GQ@mail.gmail.com>
In-reply-to <1461131542.9.0.938099488845.issue20116@psf.upfronthosting.co.za>
Content
Based on the example provided by the OP, it appears that he would expect
the output to be:
{'family': ['citrus'], 'fruits': ['lemon;lime']}

Since the W3C recommendation for the application/x-www-form-urlencoded type
specify using '&' to separate the parameters in the query string (';' is
not mentioned there), I recommended a parameter for disabling the use of
';' as a separator (but '&' will still be the separator to be used).

The only thing I see against using the RFC is that although it specifies
which characters are valid in a query string, it does not define how they
should be used; that is done by W3C's application/x-www-form-urlencoded and
it is very specific about using '&' as a separator.
History
Date User Action Args
2016-04-20 14:08:42luiz.poletosetrecipients: + luiz.poleto, orsenthil, r.david.murray, ruben.orduz
2016-04-20 14:08:42luiz.poletolinkissue20116 messages
2016-04-20 14:08:42luiz.poletocreate