With significant input from Fred I made some changes to xmlrpclib a couple
months ago to better integrate datetime objects into xmlrpclib. That raised
some problems because I neglected to add support for comparing datetime
objects with xmlrpclib.DateTime objects. (The problem showed up in
On 10/22/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
With significant input from Fred I made some changes to xmlrpclib a couple
months ago to better integrate datetime objects into xmlrpclib. That raised
some problems because I neglected to add support for comparing datetime
objects with
[EMAIL PROTECTED] wrote:
With significant input from Fred I made some changes to xmlrpclib a couple
months ago to better integrate datetime objects into xmlrpclib. That raised
some problems because I neglected to add support for comparing datetime
objects with xmlrpclib.DateTime objects.
On Saturday 22 October 2005 07:48, [EMAIL PROTECTED] wrote:
..., I'm inclined to dump support
for marshalling and comparison of time objects altogether. Do others
agree that was a bad idea?
Very much. As Jim notes, supporting date objects is more than a little
questionable as well.
Based on feedback from Jim and Fred, I took out date and time object
marshalling and comparison. (Actually, you can still compare an
xmlrpclib.DateTime object with a datetime.date object, because DateTime
objects can be compared with anything that has a timetuple method.) There's
a patch at
