As per John's request, this patch allows lossless round-tripping of
Python datetime.datetime objects.
Unfortunately, the xmlrpclib dumps() and loads() functions use funny
wrapper objects like xmlrpclib.DateTime rather than directly serializing
to/from standard Python types like datetime.datetime.
Jason Gerard DeRose wrote:
As per John's request, this patch allows lossless round-tripping of
Python datetime.datetime objects.
Unfortunately, the xmlrpclib dumps() and loads() functions use funny
wrapper objects like xmlrpclib.DateTime rather than directly serializing
to/from standard Python t
On 12/03/2009 11:56 AM, Rob Crittenden wrote:
What should this do it if the incoming DateTime value is not parsed
correctly by datetime.datetime()?
Well in theory this should never happen if the parameter value complies
with the specification which demands it be in iso8601 format. I would
im
On Thu, 2009-12-03 at 11:56 -0500, Rob Crittenden wrote:
> Jason Gerard DeRose wrote:
> > As per John's request, this patch allows lossless round-tripping of
> > Python datetime.datetime objects.
> >
> > Unfortunately, the xmlrpclib dumps() and loads() functions use funny
> > wrapper objects like
John Dennis wrote:
On 12/03/2009 11:56 AM, Rob Crittenden wrote:
What should this do it if the incoming DateTime value is not parsed
correctly by datetime.datetime()?
Well in theory this should never happen if the parameter value complies
with the specification which demands it be in iso8601
On 12/04/2009 09:49 AM, Rob Crittenden wrote:
John Dennis wrote:
On 12/03/2009 11:56 AM, Rob Crittenden wrote:
What should this do it if the incoming DateTime value is not parsed
correctly by datetime.datetime()?
Well in theory this should never happen if the parameter value
complies with th
