[ase-users] cannot import name minpack2

Bernd Hartke hartke at pctc.uni-kiel.de
Thu Apr 18 10:55:16 CEST 2013


On 04/18/2013 10:38 AM, Marcin Dulak wrote:
> On 04/17/2013 07:58 PM, Bernd Hartke wrote:
>> On 04/17/2013 07:32 PM, Marcin Dulak wrote:
>>> rpm -q python numpy python-scipy
>> This gives me:
>>
>> python-2.7.2-7.17.1.x86_64
>> package numpy is not installed
>> python-scipy-0.11.0-23.6.x86_64
>>
>> "rpm -q python python-numpy python-scipy" (which is what you probably
>> intended) gives me this:
>>
>> python-2.7.2-7.17.1.x86_64
>> python-numpy-1.7.0-62.1.x86_64
>> python-scipy-0.11.0-23.6.x86_64
> hm, i'm getting the same.
> When you do: python -c "from scipy.optimize import minpack2"
> does it fail printing the new scipy path?
> python -c "import scipy; print scipy"
> Should be /usr/lib64 ...
>
>

Confusingly, or interestingly, as root 'python -c "from scipy.optimize
import minpack2" ' produces exactly nothing. With my own userid I get
what I had before, i.e.:
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File
> "/usr/local/lib64/python2.7/site-packages/scipy/optimize/__init__.py",
> line 146, in <module>
>   File
> "/usr/local/lib64/python2.7/site-packages/scipy/optimize/optimize.py",
> line 34, in <module>
>   File
> "/usr/local/lib64/python2.7/site-packages/scipy/optimize/linesearch.py",
> line 16, in <module>
> ImportError: cannot import name minpack2

This prompted me to check $PYTHONPATH, which is simply empty for root
but contains various stuff for my own userid --- one entry comes from
the ADF package, others from me, in probably failed attempts to add in
what PYTHONPATH "should" contain besides what ADF wants (which points to
some ADF-internal python things). Hence, when I delete PYTHONPATH
completely in my userid, the command
   python -c "from scipy.optimize import minpack2"
also produces no response, probably indicating that it just works fine.

In fact, this eliminates the error I got for the hpc test.
However, now I am stuck with the (new) error in the oi test:

> ERROR: oi.py (ScriptTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/ase/test/__init__.py", line
> 54, in testfile
>     execfile(self.filename, {'display': self.display})
>   File "/usr/lib/python2.7/site-packages/ase/test/fio/oi.py", line 42,
> in <module>
>     write(fname1, atoms, format=format)
>   File "/usr/lib/python2.7/site-packages/ase/io/__init__.py", line
> 460, in write
>     write(filename, images, **kwargs)
>   File "/usr/lib/python2.7/site-packages/ase/io/png.py", line 40, in
> write_png
>     PNG(atoms, **parameters).write(filename)
>   File "/usr/lib/python2.7/site-packages/ase/io/eps.py", line 139, in
> write
>     self.write_trailer()
>   File "/usr/lib/python2.7/site-packages/ase/io/png.py", line 26, in
> write_trailer
>     x = renderer._renderer.buffer_rgba(0, 0)
> IndexError: Unexpected SeqBase<T> length.
>
> ----------------------------------------------------------------------

which I did not have after my first ASE installation attempt...

Bernd

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.fysik.dtu.dk/pipermail/ase-users/attachments/20130418/c93980fe/attachment.html>


More information about the ase-users mailing list