[issue20116] urlparse.parse_qs should take argument for query separator

Jacob Walls added the comment: Greetings. I believe this is mooted by #42967 as well as changes even prior to that. https://bugs.python.org/issue42967 -- nosy: +jacobtylerwalls ___ Python tracker _

[issue20116] urlparse.parse_qs should take argument for query separator

Kobi Gana added the comment: We are on the same page and we should also consider marked this as defect. Thanks On Sun, Feb 17, 2019 at 7:44 PM nr wrote: > > nr added the comment: > > W3C allows both constructs, ampersand and semicolon. > https://www.w3.org/TR/html401/appendix/notes.html#h-

[issue20116] urlparse.parse_qs should take argument for query separator

nr added the comment: W3C allows both constructs, ampersand and semicolon. https://www.w3.org/TR/html401/appendix/notes.html#h-B.2.2 Especially servlet containers and servers running CGI programs often use semicolons as a separator. I would say to parse either ampersands OR semicolons and ke

[issue20116] urlparse.parse_qs should take argument for query separator

Kobi Gana added the comment: Hi all, Please take the next case: The url - http://hostname.domain/mypage.asp?fields=id&query=%22((release%3D{id%3D1004});(sprint%3D{id%3D1040});(team%3D{id%3D1004});(severity%3D{id%3D%27list_node.severity.urgent%27});!phase%3D{id+IN+%27phase.defect.closed%27,%27

[issue20116] urlparse.parse_qs should take argument for query separator

Ruben D. Orduz added the comment: Hi all, OP here. My intent was to optionally pass a separator parameter, _not_ enable/disable toggle. -- ___ Python tracker ___ __

[issue20116] urlparse.parse_qs should take argument for query separator

Luiz Poleto added the comment: 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 t

[issue20116] urlparse.parse_qs should take argument for query separator

Senthil Kumaran added the comment: Luiz, The original question was about introducing a parameter to override query string separate ';'. If we do with enable or disable, then we should provide another option for query string separator. The OP provided one example of query string which had & a

[issue20116] urlparse.parse_qs should take argument for query separator

Luiz Poleto added the comment: If this bug is to be moved forward, we should consider this: The RFC 3986 defines that a query can have any of these characters: /?:@-._~!$&'()*+,;= ALPHA DIGIT %HH (encoded octet) But does not define how the data should be interpreted, leaving that to the naming

[issue20116] urlparse.parse_qs should take argument for query separator

Ruben D. Orduz added the comment: Senthil, The RFC can be found here: http://tools.ietf.org/html/rfc3986#section-2.2 -- ___ Python tracker ___ __

[issue20116] urlparse.parse_qs should take argument for query separator

Senthil Kumaran added the comment: If you could point to RFC which states the list of characters which can be used as valid query string separators, we can include that list. (Of course in 3.5) -- nosy: +orsenthil ___ Python tracker

[issue20116] urlparse.parse_qs should take argument for query separator

Ruben D. Orduz added the comment: Ah, gotcha. I think I will leave as is then. Thanks for clarifying. -- ___ Python tracker ___ ___ Py

[issue20116] urlparse.parse_qs should take argument for query separator

R. David Murray added the comment: I'm saying that this is a change that can be made only in 3.5. if you want to submit a patch here for 2.7 for other people to use that's fine, but it won't get applied. -- ___ Python tracker

[issue20116] urlparse.parse_qs should take argument for query separator

Ruben D. Orduz added the comment: So, are you suggesting I should change to a different type if desired for 2.7.x or leave for release to 3.5 and then submit a patch to backport it to 2.7.x? I apologize, not sure how the workflow works in these cases. Thanks. -- __

[issue20116] urlparse.parse_qs should take argument for query separator

R. David Murray added the comment: As an enhancement, this could only go into 3.5. -- nosy: +r.david.murray versions: +Python 3.5 -Python 2.7 ___ Python tracker ___ _

[issue20116] urlparse.parse_qs should take argument for query separator

New submission from Ruben D. Orduz: Currently urlparse.parse_qs (http://hg.python.org/cpython/file/2.7/Lib/urlparse.py#l150) assumes and uses ';' as a query string separator with no way to overwrite that. There are several web service APIs out there that use ';' as list separator (e.g. [URL]?