Patches item #1120353, was opened at 2005-02-10 15:25 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1120353&group_id=5470
Category: Library (Lib) Group: Python 2.5 Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Fredrik Lundh (effbot) Summary: better datetime support for xmlrpclib Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2005-03-17 20:27 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1120353&group_id=5470 _______________________________________________ Patches mailing list [email protected] http://mail.python.org/mailman/listinfo/patches
