Bug#576837: confirmation

Konstantinos Poulios logari81 at googlemail.com
Mon Aug 16 14:36:09 UTC 2010


This bug is still present in paraview 3.8.0-1:

>>> from paraview import servermanager
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/pymodules/python2.6/paraview/servermanager.py", line
43, in <module>
    import paraview, re, os, new, sys, vtk
  File "/usr/lib/pymodules/python2.6/paraview/vtk/__init__.py", line
4, in <module>
    from libvtkCommonPython import *
ImportError: No module named libvtkCommonPython

>>> sys.path.append('/usr/lib/paraview')
>>> from paraview import servermanager
paraview version 3.8.0, Date: 2010-03-26

I can imagine two kind of solutions:
1. Create symlinks to all /usr/lib/paraview/*Python*.so files.
2. Patch the __init__.py file of the paraview model with
"sys.path.append('/usr/lib/paraview')"

Actually it is quite the same question as here:
http://www.mail-archive.com/debian-python@lists.debian.org/msg04688.html

Furthermore the package supports pyversions >= 2.4, while it contains
private extensions which are built only against the current python
version. I think it should strictly bind to the default python
version.





More information about the debian-science-maintainers mailing list