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

2016-04-20 Thread Ruben D. Orduz
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 <http://bugs.python.org/issue20

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

2014-01-03 Thread Ruben D. Orduz
Ruben D. Orduz added the comment: Senthil, The RFC can be found here: http://tools.ietf.org/html/rfc3986#section-2.2 -- ___ Python tracker <http://bugs.python.org/issue20

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

2014-01-03 Thread Ruben D. Orduz
Ruben D. Orduz added the comment: Ah, gotcha. I think I will leave as is then. Thanks for clarifying. -- ___ Python tracker <http://bugs.python.org/issue20

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

2014-01-03 Thread Ruben D. Orduz
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

2014-01-03 Thread Ruben D. Orduz
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 s