The metator 1.3.10 wheel on PyPI embeds louvain binaries that require a very recent libc, but the wheel is not tagged that way (metator-1.3.10-py3-none-any) and seems misleadingly universal.
When manually invoking the louvain commands on a RHEL 9 (glibc 2.34) system I get:
lib/python3.11/site-packages/metator/bin/louvain: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by lib/python3.11/site-packages/metator/bin/louvain)
lib/python3.11/site-packages/metator/bin/louvain: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by lib/python3.11/site-packages/metator/bin/louvain)
From metaTOR, the error message claims the executables cannot be found (actually, they are found but cannot be run).
It would help if the louvain binaries (https://sourceforge.net/projects/louvain/) were compiled on an old system. I recompiled them on RHEL 9 and it worked.
The metator 1.3.10 wheel on PyPI embeds louvain binaries that require a very recent libc, but the wheel is not tagged that way (metator-1.3.10-py3-none-any) and seems misleadingly universal.
When manually invoking the louvain commands on a RHEL 9 (glibc 2.34) system I get:
From metaTOR, the error message claims the executables cannot be found (actually, they are found but cannot be run).
It would help if the louvain binaries (https://sourceforge.net/projects/louvain/) were compiled on an old system. I recompiled them on RHEL 9 and it worked.