Closed patham9 closed 3 months ago
Interestingly it also failed for me on Ubuntu. Compared to the Mac OS case it did not show me the error however, instead the executable is just not available in the system path after the command.
Workaround was to symlink an executable sh script with content
python3 /home/patham9/hyperon-experimental/python/hyperon/metta.py $@
to /usr/bin/metta
.
Hi Patrick, could you please clarify if you built the native code before installing Python library as described in README.md:
At some point the order was changed, before one needed to run pip install
before building binaries, now it is vice versa, so it is a common pitfall.
@patham9 can we close it?
Yes I installed the native code before installing the Python library. The instructions in the Readme work neither on Mac OS Ventura, nor on Ubuntu 22 for me. (fresh install of the latter) But the symlink workaround worked. A few months ago the instructions worked well.
@patham9, could you please add results of the following commands:
python3 --version
python3 -m pip --version
python3 -m pip list
and full log of the python3 -m pip install -e ./python[dev]
@patham9 please shout if you still can reproduce the issue. Otherwise I think we can close it.
Closing it as there is not enough information to investigate.
I can try again soon, but it should be fine for now if it didn't occur for anybody else.
The command
python3 -m pip install -e ./python[dev]
does not work anymore and instead outputs an error messageOne can still run MeTTa from the folder, but due to the issue it will not install in the standard way anymore.