[issue22618] urllib.parse.parse_qsl different results after urllib.parse.unquote

Alex Vaystikh added the comment: It is much clearer after your insight: - I wasn't aware that 'parse_qs' unquotes values. That's most helpful! - I had no idea what 'keep_blank_values' were before your example, but now it couldn't be more obvious. I know that adding that example to docs would've

[issue22618] urllib.parse.parse_qsl different results after urllib.parse.unquote

R. David Murray added the comment: Eh, that "Isn't it obvious" comment was uncalled for. Of course it isn't obvious, especially when the docs are unclear. -- ___ Python tracker ___

[issue22618] urllib.parse.parse_qsl different results after urllib.parse.unquote

R. David Murray added the comment: Isn't it obvious that you have to parse before you unquote? That's the purpose of quoting, after all. I suppose that is one of those "beginner mind" things that is obvious only because I'm an experienced programmer...and that there are web servers that do i

[issue22618] urllib.parse.parse_qsl different results after urllib.parse.unquote

Changes by Alex Vaystikh : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue22618] urllib.parse.parse_qsl different results after urllib.parse.unquote

New submission from Alex Vaystikh: parsing query-string before and after cleaning with urllib.parse.unquote can have very different results: http://nbviewer.ipython.org/gist/bornio/e112e6d8d04dfed898c8 Perhaps it should be better documented, or make the method more idempotent? -- comp