[Zope-Coders] removing more Zope decoys

[Toby Dickenson]

On Thursday 21 November 2002 7:43 am, Fred L. Drake, Jr. wrote:
> Toby Dickenson writes:
>  > The Zope version of xmlrpclib is not exactly the same as the standar=
d
>  > python version. The differences relate to marshalling python types i=
nto
>  > xml: The standard python version cant marshal a python 'None'. Also
>  > there are some patches around that have special handling for some Zo=
pe
>  > classes: DateTime, File, Image. (this patch missed the deadline for
>  > 2.6).
>
> There's actually a good reason <nil/> isn't supported by the standard
> xmlrpclib module: it's not part of the XML-RPC specification, so it's
> not really interoperable.  I'd love to know of a way to determine
> whether the system on the other end of the connection supports it
> (request header, etc.), but am not aware of a way to do this.  The
> extension proposal for <nil/> doesn't provide for this, and the only
> other implementation I know of that supports it is one of the Java
> implementations (where <nil/> maps to null).

Yes. The current Zope xmlrpclib marshalls a python None as an xmlrpc bool=
ean=20
false. There are good reasons why we dont want *that* in the standard=20
version.