On windows, using installs from conda, the compiled libutils module cannot be loaded. This is because the libutils loading code expects the file to be called libutils.pyd, but conda now calls it something like: libutils.cp37_win-amd64.pyd.
This is mostly a packaging issue, but needs a small code change to cope with the change to the naming scheme for compiled files. This needs to be compared to Linux and MacOS as well, and check that it still works from source.
If someone on Windows runs into this bug you can get around it by renaming the file located at:
...\miniconda3\envs\eqcorrscan\lib\site-packages\eqcorrscan\utils\lib\libutils.XXXXX.pyd to libutils.pyd.
On windows, using installs from conda, the compiled libutils module cannot be loaded. This is because the libutils loading code expects the file to be called libutils.pyd, but conda now calls it something like: libutils.cp37_win-amd64.pyd.
This is mostly a packaging issue, but needs a small code change to cope with the change to the naming scheme for compiled files. This needs to be compared to Linux and MacOS as well, and check that it still works from source.
If someone on Windows runs into this bug you can get around it by renaming the file located at: ...\miniconda3\envs\eqcorrscan\lib\site-packages\eqcorrscan\utils\lib\libutils.XXXXX.pyd to libutils.pyd.