James Addison added the comment:
Thanks Senthil; please take your time. This isn't urgent, and would likely
benefit from further standardization of the URL query string and/or
form-encoded data formats (outside the Python project) to achieve consensus.
A fully-considered answer at a
James Addison added the comment:
No problem, and thanks for the heads-up Tal! I'll raise this as a topic on
python-dev if it still seems worth pursuing, after collecting some more
thoughts about it.
--
___
Python tracker
&
James Addison added the comment:
NB: There appears to be some relevant discussion in
https://github.com/whatwg/url/issues/469
--
___
Python tracker
<https://bugs.python.org/issue18
James Addison added the comment:
The pair of pull requests below implement None-preserving urlencode and
parse_qs* via a default-disabled flag 'standalone_keys'.
- https://bugs.python.org/pull_request19259
- https://bugs.python.org/pull_request19264
(they're also already l
Change by James Addison :
--
pull_requests: +19264
pull_request: https://github.com/python/cpython/pull/19949
___
Python tracker
<https://bugs.python.org/issue18
Change by James Addison :
--
pull_requests: +19259
pull_request: https://github.com/python/cpython/pull/19945
___
Python tracker
<https://bugs.python.org/issue18
James Addison added the comment:
Chiming in here to add that I'd appreciate the ability to render 'standalone'
(i.e. no '=') query-string keys in order to distinguish between
absence-of-value and empty-string situations.
The backwards-compatibility concerns in her
