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 kj
Recipients AdamGold, eric.araujo, kj, lemburg, orsenthil, serhiy.storchaka, vstinner
Date 2021-01-23.16:41:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I updated the PR to take in a sequence of separators from the user - eg:

>>> urllib.parse.parse_qsl('a=1&b=2;c=3', separators=('&', ';'))
[('a', '1'), ('b', '2'), ('c', '3')]
>>> urllib.parse.parse_qsl('a=1&b=2;c=3', separators=('&',))
[('a', '1'), ('b', '2;c=3')]

I _didn't_ change the default - it will allow both '&' and ';' still. Eric showed a link above that still uses semicolon. So I feel that it's strange to break backwards compatibility in a patch update. Maybe we can make just '&' the default in Python 3.10, while backporting the ability to specify separators to older versions so it's up to users?

I'm not sure, any thoughts on this? Opinions would be greatly appreciated.
Date User Action Args
2021-01-23 16:42:00kjsetrecipients: + kj, lemburg, orsenthil, vstinner, eric.araujo, serhiy.storchaka, AdamGold
2021-01-23 16:42:00kjsetmessageid: <>
2021-01-23 16:42:00kjlinkissue42967 messages
2021-01-23 16:41:59kjcreate