Print

Print


Right, I hadn't chased through the Cing code but it looks like they have 
some use of those import modules not in functions but at file level so 
already called at import time rather than at use time, so you did exactly 
the right thing.

(I still think Mr Python ought to do something about urllib2.  I mean if 
you ship a pre-compiled Python to someone then any code that uses urllib2 
is possibly going to fail.)

(Well, we could also build and ship openssl, but where does one stop?!?)

Wayne

On Wed, 8 Apr 2009, Kaare Teilum wrote:

> Yes, on one of the systems we have libssl.so.0.9.7 and on the other we only
> have libssl3.so
>
> Anyway, I used your quick-fix which gave:
>
> Traceback (most recent call last):
>  File
> "/sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/ccpnmr/analysis/AnalysisGui.py",
> line 81, in <module>
>    from ccpnmr.analysis.AnalysisPopup import AnalysisPopup
>  File
> "/sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/ccpnmr/analysis/AnalysisPopup.py",
> line 153, in <module>
>    from nijmegen.cing.CingPopup import CingPopup
>  File
> "/sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/nijmegen/cing/CingPopup.py",
> line 5, in <module>
>    from nijmegen.cing.CingFrame import CingFrame
>  File
> "/sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/nijmegen/cing/CingFrame.py",
> line 23, in <module>
>    from nijmegen.cing import iCingRobot
>  File
> "/sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/nijmegen/cing/iCingRobot.py", line
> 268, in <module>
>    BOUNDARY = mimetools.choose_boundary()
> NameError: name 'mimetools' is not defined
>>>>
>
> If I instead of commenting out line 6 in the iCingRobot.py just remove
> urllib2 it appears to work. So in iCingRobot.py I did:
>
> #import urllib2, httplib, mimetypes, mimetools
> import httplib, mimetypes, mimetools
>
> Thanks for your help,
> Kaare
>
> On Wed, 8 Apr 2009 10:11:56 +0100, Wayne Boucher <[log in to unmask]>
> wrote:
>
>> So if you do (at the operating system prompt):
>>
>>   ls -l /usr/lib/libssl*
>>
>> on the computer it was compiled on (i.e. our one) you get:
>>
>>   lrwxrwxrwx 1 root root     15 2008-03-03 10:36 /usr/lib/libssl.so ->
> libssl.so.0.9.8
>>   -rwxr-xr-x 1 root root 214396 2008-02-28 18:48 /usr/lib/libssl.so.0.9.7
>>   -r-xr-xr-x 1 root root 271584 2007-10-18 00:09 /usr/lib/libssl.so.0.9.8
>>
>> So my guess is you have 0.9.7 or older.  Hopefully you can find 0.9.8
>> (this is the nightmare of pre-compiled code, it assumes certain system
>> libraries are in place and even if they are off by one minor version it
>> all goes to pot).
>>
>> If you can't get that version then a quick fix (while Tim looks at this)
>> is to edit:
>>
>>   /sbinlab2/software/x32/ccpnmr/ccpnmr2.0/python/nijmegen/cing/iCingRobot.py
>>
>> and comment out the import statement on line 6:
>>
>>   #import urllib2, httplib, mimetypes, mimetools
>>
>> Wayne
>>
>> On Wed, 8 Apr 2009, Kaare Teilum wrote:
>>
>>> Hi Wayne
>>>
>>> If I do as you suggest I get:
>>>
>>> Python 2.5.2 (r252:60911, Apr  6 2009, 18:37:16)
>>> [GCC 4.2.1 (SUSE Linux)] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> import _hashlib
>>> Traceback (most recent call last):
>>>  File "<stdin>", line 1, in <module>
>>> ImportError: libssl.so.0.9.8: cannot open shared object file: No such file
>>> or directory
>>>
>>> If I do the same thing on a 64-bit installation I get:
>>>
>>> Python 2.5.2 (r252:60911, Apr  6 2009, 17:53:27)
>>> [GCC 4.1.2 20070115 (prerelease) (SUSE Linux)] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> import _hashlib
>>> Traceback (most recent call last):
>>>  File "<stdin>", line 1, in <module>
>>> ImportError: No module named _hashlib
>>>
>>> Kaare
>>>
>>> On Wed, 8 Apr 2009 08:47:30 +0100, Wayne Boucher <[log in to unmask]>
>>> wrote:
>>>
>>>> Hmmm, that's bad!  So maybe it's something else that's missing.  If you
>>>> run /sbinlab2/software/x32/ccpnmr/python2.5/bin/python and do:
>>>>
>>>> >>> import _hashlib
>>>>
>>>> does it give any kind of error message?  That is the most likely cause of
>>>> the error that then leads onto the reported error.
>>>>
>>>> Wayne
>>>>
>>>> On Wed, 8 Apr 2009, Kaare Teilum wrote:
>>>>
>>>>> Hi Wayne
>>>>>
>>>>> On both the 32-bit systems I have tried /usr/lib/libssl3.so is present...
>>>>>
>>>>> Kaare
>>>>>
>>>
>