[Catalog-sig] Fwd: [XML-SIG] Something's definitely wrong...
ssteinerx at gmail.com
Fri Jan 22 18:26:38 CET 2010
This is copied from the XML-SIG which doesn't seem to be too heavily followed...
I'm working on finishing up my pypi metadata mirror and have run into an apparent XML-RPC MultiCall issue.
This is using the MultiCall RPC interface on PyPi with my currently unversioned "pypimirror" user-agent (in case someone who as access could look in the PyPI logs for the bombing call).
Anyone used this interface on PyPI and/or have any ideas on this?
>> From: "Dieter Maurer" <dieter at handshake.de>
>> Date: January 21, 2010 8:42:09 AM EST
>> To: "ssteiner at idc" <ssteiner at integrateddevcorp.com>
>> Cc: xml-sig at python.org
>> Subject: Re: [XML-SIG] Something's definitely wrong...
>> ssteiner at idc wrote at 2010-1-20 08:43 -0500:
>>> I'm using the xmlrpc MultiCall class pretty heavily in an application and every time I've somehow caused an error in the xmlrpclib.py code, I get an exception trying to raise the exception.
>>> Here's the most recent example:
>>> grouped = grouper(2, tuple(mc_result))
>>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1001, in __getitem__
>>> raise Fault(item['faultCode'], item['faultString'])
>>> Fault: <Fault 1: "<type 'exceptions.TypeError'>:'NoneType' object is unsubscriptable">
>> You see here the client side code to report that an exception
>> has happened on the server side.
>> The "TypeError" was not raised at this place but on the server side.
>> Here, a "Fault" is (successfully) raised with "faultCode" 1 and "faultString"
>> "<type 'exceptions.TypeError'>:'NoneType' object is unsubscriptable">.
>> If you are lucky, the server side has logged information for
>> the raised exception. If not, you need to convince the server side
>> to do so.
>> XML-SIG maillist - XML-SIG at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalog-SIG