Why doesn't xmlrpclib.dumps just dump an empty value instead of<nil/>?

[martin f krafft]

Hi,

xmlrpclib.dumps ((None,), allow_none=True ) yields

'<params>\n<par am>\n<value><ni l/></value></param>\n</params>\n'

Why doesn't it just yield

'<params>\n<par am>\n<value/></param>\n</params>\n'

Or even just

'<params>\n<par am/>\n</params>\n'

Those are valid XML and valid XML-RPC, but <nil/isn't.

Thanks for any thoughts...

--
martin | http://madduck.net/ | http://two.sentenc.es/

a farmer is a man outstanding in his field.

spamtraps: madduck.bogus@m adduck.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH3R7kIgv IgzMMSnURAiKSAK C9gq4Ysnuy1Rm3Y x2SArCM0iOcSgCg sTKk
E4v2x0l/23PS2Mz8DqakOg0 =
=C0Qw
-----END PGP SIGNATURE-----

[Marc 'BlackJack' Rintsch]

Re: Why doesn't xmlrpclib.dumps just dump an empty value instead of&lt;nil/&gt;?

On Sun, 16 Mar 2008 14:21:40 +0100, martin f krafft wrote:

Hi,
>
xmlrpclib.dumps ((None,), allow_none=True ) yields
>
'<params>\n<par am>\n<value><ni l/></value></param>\n</params>\n'
>
Why doesn't it just yield
>
'<params>\n<par am>\n<value/></param>\n</params>\n'
>
Or even just
>
'<params>\n<par am/>\n</params>\n'
>
Those are valid XML and valid XML-RPC, but <nil/isn't.

In XML-RPC there is no `None`, so there's the non standard `allow_none`
Option to allow `None` to be represented as ``<nil/>``.

And is an empty <param/or <value/really valid XML-RPC?

Ciao,
Marc 'BlackJack' Rintsch