Thank you for your review Terry.

You can pass an integer in range from -2147483648 to 2147483647, and it is marshalled using the <int> tag. But when you receive tags <i1>, <i2>, etc, they are unmarshalled to integer values, and these values can be out of range from -2147483648 to 2147483647. How to document all these detail in short?

The same is with other types. xmlrpclib is more conservative with data that it sends than with data that it receives. float is marshalled using the <double> flag, but the <float> tag is unmarshalled to float too. None and datetime can be marshalled only if corresponding option is enabled, but always can be unmarshalled. Decimal can't be marshalled, but can be unmarshalled.

For now unmarshalling None is supported from the <nil> tag (this is unofficial extension). But Apache XML-RPC server produces tags with namespace: <ex:nil>, which is not supported in xmplrpclib. The patch adds the support of tags with namespaces, and therefore adds the support of unmarshalling None in Apache XML-RPC server format.