R. David Murray added the comment:
In Python the str of a None value is indeed 'None', just as the str of a True
value is 'True'. Unless the protocol to which you are encoding supports null
values, you shouldn't be using None values in the input to the serialization.
If you want an empty string in the output, use an empty string in the input.
Now, that said, it seems to me that while it is not (apparently) RFC compliant,
query strings do have a natural way to support null values: a name without a
value. It would therefore be convenient if urlencode supported null values by
turning something like {'josh': None, 'fred': 'abc'} into:
josh&fred=abc
That is what I would expect it to do, so I'd be in favor of that enhancement.
I note that parse_qs and parse_qsl don't handle this case either, which
surprises me since I think such value-less query string parameters are fairly
common.
----------
nosy: +r.david.murray
stage: -> needs patch
type: behavior -> enhancement
versions: +Python 3.4 -Python 2.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue18857>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
