homepage

This patch makes it possible for an application to ask
that datetime objects be used instead of
xmlrpclib.DateTime instances.
I'm submitting this as a patch instead of checking this
in since it's a more invasive change to Fredrik's
module than my earlier change to make it accept
datetime objects as valid date/time values.

Logged In: YES 
user_id=44345
I just implemented something similar in a copy of xmlrpclib I installed on
a 2.3 system. In addition to allowing <dateTime.iso8601> strings to
decode to datetime.datetime objects, I allowed datetime.time and
datetime.date objects as input. The former is accomodated by
setting the date part to the current date, the latter by setting the time
to 00:00:00.
Fredrik, any comment? I think it would improve the transparency of
Python's xmlrpc interface if datetime objects worked at both ends of
the transmission.

Logged In: YES 
user_id=38376
I don't have time to review the patches, but I agree that this 
would be a good thing, and that it's better to support it at 
both ends.
Skip, I'm assigning this one to you. Can you check Fred's 
patch, merge relevant portions with your patch, and check it 
all in?

Logged In: YES 
user_id=44345
libxmlrpclib.tex 1.23, xmlrpclib.py 1.41, test_xmlrpc.py 1.9