Thomas Fenzl added the comment:
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
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 2.7, Python 3.2 -Python 2.5, Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2623
___
Changes by Skip Montanaro s...@pobox.com:
--
nosy: -skip.montanaro
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2623
___
___
Python-bugs-list
Changes by Skip Montanaro s...@pobox.com:
--
assignee: skip.montanaro -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2623
___
___
Leonard Clark [EMAIL PROTECTED] added the comment:
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
Skip Montanaro [EMAIL PROTECTED] added the comment:
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
Changes by Skip Montanaro [EMAIL PROTECTED]:
--
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2623
__
___
Python-bugs-list mailing list
Changes by Ralf Schmitt [EMAIL PROTECTED]:
--
nosy: +schmir
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2623
__
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Leonard Clark [EMAIL PROTECTED]:
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
