From murphy40 at uni.edu  Fri Jan 15 16:34:45 2010
From: murphy40 at uni.edu (ryan murphy)
Date: Fri, 15 Jan 2010 09:34:45 -0600 (CST)
Subject: [XML-SIG] pyXML
Message-ID: <22660127.1263569685837.JavaMail.ocsmidp@cecil.collab.uni.edu>

When I try to build pyXML in ubuntu 9.10 I get the following error

'gcc' failed with error status 1.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/xml-sig/attachments/20100115/0781841e/attachment.htm>

From stefan_ml at behnel.de  Fri Jan 15 19:19:25 2010
From: stefan_ml at behnel.de (Stefan Behnel)
Date: Fri, 15 Jan 2010 19:19:25 +0100
Subject: [XML-SIG] pyXML
In-Reply-To: <22660127.1263569685837.JavaMail.ocsmidp@cecil.collab.uni.edu>
References: <22660127.1263569685837.JavaMail.ocsmidp@cecil.collab.uni.edu>
Message-ID: <4B50B1AD.7070109@behnel.de>


ryan murphy, 15.01.2010 16:34:
> When I try to build pyXML in ubuntu 9.10 I get the following error
> 
> 'gcc' failed with error status 1.

Please provide a complete error report. The above line is meaningless.

Also note that PyXML is no longer maintained. If you are looking for a
state-of-the-art XML library, use ElementTree or lxml.

Stefan

From ssteinerx at gmail.com  Sat Jan 16 03:47:03 2010
From: ssteinerx at gmail.com (ssteinerX@gmail.com)
Date: Fri, 15 Jan 2010 21:47:03 -0500
Subject: [XML-SIG] xmlrpclib.py exception while trying to raise exception
Message-ID: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>

Hi!

Not totally sure this is the right list for this but...

This just popped up in a program that has successfully (in this run) made thousands of multicall()s.

Then, out of the blue, this came up.

I couldn't find anything like this in the bug tracker.

Anyone have any clues about why the exception itself wouldn't be defined or should I just file a bug?

Thanks,

S
aka/ssteinerX
aka/Steve Steiner

  mc_result = multicall()                                                                                         
File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1042,                   
in __call__                                                                                                         
    return MultiCallIterator(self.__server.system.multicall(marshalled_list))                                       
  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1199, in __call__                                                                                                         
    return self.__send(self.__name, args)                                                                           
  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1489, in __request                                                                                                       
    verbose=self.__verbose                                                                                          
  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1253, in request                                                                                                         
    return self._parse_response(h.getfile(), sock)                                                                  
  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1392, in _parse_response                                                                                                  
    return u.close()                                                                                                
  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 838, in close                                                                                                              
    raise Fault(**self._stack[0])                                                                                   
Fault: <Fault 1: "<type 'exceptions.NameError'>:global name 'Fault' is not defined">



From martin at v.loewis.de  Sat Jan 16 19:23:40 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 16 Jan 2010 19:23:40 +0100
Subject: [XML-SIG] xmlrpclib.py exception while trying to raise exception
In-Reply-To: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
References: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
Message-ID: <4B52042C.10606@v.loewis.de>

> Anyone have any clues about why the exception itself wouldn't be defined or should I just file a bug?

This is probably during Python shutdown. Python is in the process of
clearing all module dictionaries, and then some destructor still wants
to find the Fault class.

You should make sure that all connections get closed properly before
shutting down Python.

Regards,
Martin

From ssteinerx at gmail.com  Sat Jan 16 19:46:33 2010
From: ssteinerx at gmail.com (ssteinerX@gmail.com)
Date: Sat, 16 Jan 2010 13:46:33 -0500
Subject: [XML-SIG] xmlrpclib.py exception while trying to raise exception
In-Reply-To: <4B52042C.10606@v.loewis.de>
References: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
	<4B52042C.10606@v.loewis.de>
Message-ID: <8EDA008A-3D7A-4F7B-BC2D-D25471DA72DD@gmail.com>


On Jan 16, 2010, at 1:23 PM, Martin v. L?wis wrote:

>> Anyone have any clues about why the exception itself wouldn't be defined or should I just file a bug?
> 
> This is probably during Python shutdown. Python is in the process of
> clearing all module dictionaries, and then some destructor still wants
> to find the Fault class.
> 
> You should make sure that all connections get closed properly before
> shutting down Python.

Ok, this seems to have happened at the end of a script and it looks like an exception when it was trying to shut down the xmlrpc connection.

S


From dieter at handshake.de  Sun Jan 17 08:21:53 2010
From: dieter at handshake.de (Dieter Maurer)
Date: Sun, 17 Jan 2010 08:21:53 +0100
Subject: [XML-SIG] xmlrpclib.py exception while trying to raise exception
In-Reply-To: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
References: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
Message-ID: <19282.47761.705998.75432@gargle.gargle.HOWL>

ssteinerX at gmail.com wrote at 2010-1-15 21:47 -0500:
>This just popped up in a program that has successfully (in this run) made thousands of multicall()s.
> ...
>Anyone have any clues about why the exception itself wouldn't be defined or should I just file a bug?
> ...
>File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1042,                   
>in __call__                                                                                                         
>    return MultiCallIterator(self.__server.system.multicall(marshalled_list))                                       
>  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1199, in __call__                                                                                                         
>    return self.__send(self.__name, args)                                                                           
>  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1489, in __request                                                                                                       
>    verbose=self.__verbose                                                                                          
>  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1253, in request                                                                                                         
>    return self._parse_response(h.getfile(), sock)                                                                  
>  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1392, in _parse_response                                                                                                  
>    return u.close()                                                                                                
>  File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 838, in close                                                                                                              
>    raise Fault(**self._stack[0])                                                                                   
>Fault: <Fault 1: "<type 'exceptions.NameError'>:global name 'Fault' is not defined">

Almost surely, the "NameError" comes from your XMLRPC server, not
the XMLRPC client.

If you are lucky, your server logs sufficient information for exceptions
(e.g. the traceback) to allow you to find out where the exception
occurred.



-- 
Dieter

From ssteinerx at gmail.com  Sun Jan 17 13:21:06 2010
From: ssteinerx at gmail.com (ssteinerX@gmail.com)
Date: Sun, 17 Jan 2010 07:21:06 -0500
Subject: [XML-SIG] xmlrpclib.py exception while trying to raise exception
In-Reply-To: <19282.47761.705998.75432@gargle.gargle.HOWL>
References: <9EE8FB7A-F017-44EB-AA0B-7A16D3318FC9@gmail.com>
	<19282.47761.705998.75432@gargle.gargle.HOWL>
Message-ID: <0819C315-4C46-4FA1-BF35-400AF04DFB8A@gmail.com>


On Jan 17, 2010, at 2:21 AM, Dieter Maurer wrote:

> ssteinerX at gmail.com wrote at 2010-1-15 21:47 -0500:
>> This just popped up in a program that has successfully (in this run) made thousands of multicall()s.
>> ...
>> Anyone have any clues about why the exception itself wouldn't be defined or should I just file a bug?
>> ...
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1042,                   
>> in __call__                                                                                                         
>>   return MultiCallIterator(self.__server.system.multicall(marshalled_list))                                       
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1199, in __call__                                                                                                         
>>   return self.__send(self.__name, args)                                                                           
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1489, in __request                                                                                                       
>>   verbose=self.__verbose                                                                                          
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1253, in request                                                                                                         
>>   return self._parse_response(h.getfile(), sock)                                                                  
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 1392, in _parse_response                                                                                                  
>>   return u.close()                                                                                                
>> File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/xmlrpclib.py", line 838, in close                                                                                                              
>>   raise Fault(**self._stack[0])                                                                                   
>> Fault: <Fault 1: "<type 'exceptions.NameError'>:global name 'Fault' is not defined">
> 
> Almost surely, the "NameError" comes from your XMLRPC server, not
> the XMLRPC client.
> 
> If you are lucky, your server logs sufficient information for exceptions
> (e.g. the traceback) to allow you to find out where the exception
> occurred.

Thanks.  Unfortunately I don't have access to the remote -- it's a service run by another company.

This seems to have occurred during shutdown when the connection was trying to close itself but the Fault object had already been removed.

Thanks,

S


From ssteiner at idc  Wed Jan 20 14:43:26 2010
From: ssteiner at idc (ssteiner at idc)
Date: Wed, 20 Jan 2010 08:43:26 -0500
Subject: [XML-SIG] Something's definitely wrong...
Message-ID: <14878B06-DB4A-4454-A777-E83D0CF8D2F0@integrateddevcorp.com>

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">

I could understand if I was making some sort of coding error, then getting an error, but the Fault object itself, whenever it is used, seems to be generating some sort of new error either through its use, or, as above, the code attempting to construct the Fault object fails.

The thing that's confusing about the above error is that there's a check, just before the line of code that fails, that explictly checks whether the type of "item" == type({}): so the code shouldn't even get called with "NoneType".

This all smells horribly like corrupt memory so I'm hoping someone on this list has seen symptoms like this and can point me in the right direction to start tracking this down.

This, btw, is a pretty simple, maybe 200 line pure Python app that is using the XML-RPC interface, SQLite, and zlib functions.

I'm wondering if an earlier, uncaught error is actually setting this up but it's only happened about 4 times, at completely unpredictable times, and doesn't seem to be repeatable.

Definitely in line for best bug report ever.

Anyone seen this specific symptom, regardless of cause?

S

Stephen F. Steiner
Integrated Development Corporation
ssteiner at integrateddevcorp.com
www.integrateddevcorp.com 
(603)433-1232




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/xml-sig/attachments/20100120/3d22721f/attachment.htm>

From dieter at handshake.de  Thu Jan 21 14:42:09 2010
From: dieter at handshake.de (Dieter Maurer)
Date: Thu, 21 Jan 2010 14:42:09 +0100
Subject: [XML-SIG] Something's definitely wrong...
In-Reply-To: <14878B06-DB4A-4454-A777-E83D0CF8D2F0@integrateddevcorp.com>
References: <14878B06-DB4A-4454-A777-E83D0CF8D2F0@integrateddevcorp.com>
Message-ID: <19288.22961.368767.299890@gargle.gargle.HOWL>

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.



-- 
Dieter

From ssteiner at integrateddevcorp.com  Thu Jan 21 14:55:20 2010
From: ssteiner at integrateddevcorp.com (ssteiner@idc)
Date: Thu, 21 Jan 2010 08:55:20 -0500
Subject: [XML-SIG] Something's definitely wrong...
In-Reply-To: <19288.22961.368767.299890@gargle.gargle.HOWL>
References: <14878B06-DB4A-4454-A777-E83D0CF8D2F0@integrateddevcorp.com>
	<19288.22961.368767.299890@gargle.gargle.HOWL>
Message-ID: <8E3F1024-74BE-4FDE-ACDD-46A6FCE1B0E6@integrateddevcorp.com>


On Jan 21, 2010, at 8:42 AM, Dieter Maurer wrote:

> 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.

Thanks, this is the first time I've used this particular interface; I'll forward to the site operator.

Thanks again,

S