Author schmir
Recipients georg.brandl, schmir, shrike
Date 2008-05-29.08:14:23
SpamBayes Score 0.00223963
Marked as misclassified No
Message-id <1212048866.01.0.547245243019.issue2985@psf.upfronthosting.co.za>
In-reply-to
Content
I think it's also a bug that xmlrpclib just ignores unknown tags
(without even printing a warning).

and: wouldn't it be nice if we could also write back those integers?

>>> import xmlrpclib
>>> xmlrpclib.dumps((2**40,))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ralf/pydev/trunk/Lib/xmlrpclib.py", line 1126, in dumps
data = m.dumps(params)
  File "/home/ralf/pydev/trunk/Lib/xmlrpclib.py", line 671, in dumps
dump(v, write)
  File "/home/ralf/pydev/trunk/Lib/xmlrpclib.py", line 693, in __dump
f(self, value, write)
  File "/home/ralf/pydev/trunk/Lib/xmlrpclib.py", line 704, in dump_int
raise OverflowError, "int exceeds XML-RPC limits"
OverflowError: int exceeds XML-RPC limits

I asked about the implementations supporting this as this i8 tag does
not conform to the xmlrpc spec (but I would be happy if there was an de
facto standard for sending large integers and would also help implement it).
History
Date User Action Args
2008-05-29 08:14:26schmirsetspambayes_score: 0.00223963 -> 0.00223963
recipients: + schmir, georg.brandl, shrike
2008-05-29 08:14:26schmirsetspambayes_score: 0.00223963 -> 0.00223963
messageid: <1212048866.01.0.547245243019.issue2985@psf.upfronthosting.co.za>
2008-05-29 08:14:25schmirlinkissue2985 messages
2008-05-29 08:14:23schmircreate