xmlrpclib ignores datetime parameter timezone information.  Two spots
were identified to apply a new formatting function, _iso8601format, to
ensure that the timezone is passed to the server.

I would like this fix to be included in future releases. (Thank you!)

Leonard,

Can you reformulate your patch in terms of the current xmlrpclib module
code?  It no longer applies cleanly.  Also, to be considered it will
definitely need new test cases and may well need documentation changes.

Also, note that the XML-RPC "spec" is notoriously vague.  If you're
going to be messing about with the serialized form of datetime objects I
think you'll need to demonstrate that it doesn't break interoperability
with implementations for other languages.

While the XML-RPC spec is vague with regards to respecting time zone
information, the iso8601 document is not vague as to how to properly
serialize it.

Some XML-RPC libraries (like ours) completely ignore time zone
information.  I will make every effort to test this against as many
libraries as I can.

While I'm at it, I'll see about adding support for time zone information
in server results.

Is this still relevant?
The new xmlrcp.client still dumps both naive and aware datetimes as ISO 8601 strings without timezone information. xmlrpc.client.DateTime does not handle ISO 8601 with timezone information. 

So if it is, it could be updated to using strings without timezone for naive datetimes and with timezone for aware. Not sure if that could break clients parsing the xml themselves.