m3c2 Implementation Returns Incorrect Distance Values in pip Install vs. Source Build

[tabernig]

When installing py4dgeo using python -m pip install py4dgeo, the m3c2 implementation returns the same distance value for every corepoint. In contrast, when py4dgeo is built from source, each corepoint receives a unique (and correct) distance value. Notably, the uniform distance value (in the pip-installed version) is identical to the first corepoint’s distance as computed in the source build.