FS#73277 - [paraview] pvpython -c "import paraview" does not work

Attached to Project: Community Packages
Opened by Jakub Klinkovský (lahwaacz) - Thursday, 06 January 2022, 13:08 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Saturday, 23 July 2022, 19:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bruno Pagani (ArchangeGabriel)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Somehow pypython can't import the "paraview" python module:

$ pvpython -c "import paraview"
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'paraview'

Is this related to Python 3.10?
This task depends upon

Closed by  Bruno Pagani (ArchangeGabriel)
Saturday, 23 July 2022, 19:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  paraview 5.10.1-9.
Comment by Jakub Klinkovský (lahwaacz) - Thursday, 06 January 2022, 14:03 GMT
Seems to be an upstream issue: https://gitlab.kitware.com/paraview/paraview/-/issues/21152
Comment by Bruno Pagani (ArchangeGabriel) - Friday, 18 March 2022, 15:05 GMT
It works for me though… so very strange.
Comment by Bruno Pagani (ArchangeGabriel) - Saturday, 19 March 2022, 22:14 GMT
And now while wanting to try a packaging under `/opt`, it does not work. Even using the old packages (-11 with cgns 4.2) does not work anymore. Strange… I’ll try backporting upstream patch then.
Comment by Bruno Pagani (ArchangeGabriel) - Saturday, 19 March 2022, 22:48 GMT
And it just worked again, without patching…

$ pvpython -c "import paraview"
--------------------------------------------------------------------------
The library attempted to open the following supporting CUDA libraries,
but each of them failed. CUDA-aware support is disabled.
libcuda.so.1: cannot open shared object file: No such file or directory
libcuda.dylib: cannot open shared object file: No such file or directory
/usr/lib64/libcuda.so.1: cannot open shared object file: No such file or directory
/usr/lib64/libcuda.dylib: cannot open shared object file: No such file or directory
If you are not interested in CUDA-aware support, then run with
--mca opal_warn_on_missing_libcuda 0 to suppress this message. If you are interested
in CUDA-aware support, then try setting LD_LIBRARY_PATH to the location
of libcuda.so.1 to get passed this issue.
--------------------------------------------------------------------------
Python 3.10.2 (main, Jan 15 2022, 19:56:27) [GCC 11.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
Comment by Bruno Pagani (ArchangeGabriel) - Wednesday, 23 March 2022, 13:31 GMT
Still works on 5.10.1-1 for me.
Comment by Jakub Klinkovský (lahwaacz) - Thursday, 24 March 2022, 16:32 GMT
I've just tried paraview-5.10.1-1 and it seems to work fine. I guess upstream changed something and did not update their bug reports...
Comment by Daniel Klagges (Kitpaddel) - Wednesday, 30 March 2022, 20:39 GMT
This problem is still present for me with paraview-5.10.1-3 (manjaro unstable user). Any news on how to solve this?
Comment by Jakub Klinkovský (lahwaacz) - Monday, 11 April 2022, 09:12 GMT
I've run into another issue with pvpython that might be related to Python 3.10: https://gitlab.kitware.com/paraview/paraview/-/issues/21352
Comment by Bruno Pagani (ArchangeGabriel) - Friday, 22 July 2022, 14:28 GMT
Does anyone still see this issue?
Comment by Jakub Klinkovský (lahwaacz) - Saturday, 23 July 2022, 17:27 GMT
This seems to be fixed.

Loading...