Closed pavel-po closed 1 month ago
Thank you @pavel-po for reporting this, and sorry for the delayed response. Are you still seeing this issue?
After trying to reproduce it with a fresh build, I noticed that it is sensitive to the version of python with which it has been built. As long as the version of python is the same as the one that was used to compile nda, everything works. If the python version used for running is different from the one used to build it, the issue appears. I suspect this has to do with how the *.so library is named at the compilation step:
_h5py.cpython-39-x86_64-linux-gnu.so
- works for python 3.9.16
_h5py.cpython-310-x86_64-linux-gnu.so
- works for python 3.10.10
Thank you @pavel-po for the additional information. Running with a different Python Version that the one you used to compile the python bindings can indeed lead to the problem you observe. We are considering if we can catch this with a runtime check.
This runtime-check was now added to Cpp2Py, c.f. https://github.com/TRIQS/cpp2py/commit/7e539d4938ec919369d6284a4f63f6a40274dca2
Description
With a high version of python3, I get error like this one using h5:
Steps to Reproduce
The issue happens on Rusty with
Python 3.10.10
. The issue does not happen withPython 3.9.16
. I do not see dependence on any other loaded module.Versions