Message86010
Prior versions of xmlrpclib.loads would raise an exception when passed
malformed documents:
exarkun@bigdog24:~/_trial_temp$ python2.4 -c 'from xmlrpclib import
loads; loads("\x00\n<methodResponse>\n <params>\n <param>\n </param>\n
</params>\n</methodResponse>\n")'
Traceback (most recent call last):
File "<string>", line 1, in ?
File "/usr/lib/python2.4/xmlrpclib.py", line 1079, in loads
p.feed(data)
File "/usr/lib/python2.4/xmlrpclib.py", line 527, in feed
self._parser.Parse(data, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 2,
column 0
However, as of the most recent Python 2.5 and Python 2.6 point releases,
this is no longer the case:
exarkun@bigdog24:~/_trial_temp$ python2.5 -c 'from xmlrpclib import
loads; loads("\x00\n<methodResponse>\n <params>\n <param>\n </param>\n
</params>\n</methodResponse>\n")'
exarkun@bigdog24:~/_trial_temp$ python2.6 -c 'from xmlrpclib import
loads; loads("\x00\n<methodResponse>\n <params>\n <param>\n </param>\n
</params>\n</methodResponse>\n")'
exarkun@bigdog24:~/_trial_temp$
Previous versions of Python 2.5 and Python 2.6 did not exhibit this
misbehavior. |
|
Date |
User |
Action |
Args |
2009-04-16 00:20:00 | exarkun | set | recipients:
+ exarkun |
2009-04-16 00:19:59 | exarkun | set | messageid: <1239841199.24.0.504542013197.issue5767@psf.upfronthosting.co.za> |
2009-04-16 00:19:53 | exarkun | link | issue5767 messages |
2009-04-16 00:19:49 | exarkun | create | |
|