homepage

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	skip.montanaro
Date	2005年03月18日.02:27:21
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
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.

Content

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.

History
Date	User	Action	Args
2007年08月23日 15:41:46	admin	link	issue1120353 messages
2007年08月23日 15:41:46	admin	create