Closed jarpy closed 3 years ago
Aha! As long as the current working direcory is not the source directory, it works.
root@03b9f0f72677:/usr/src/pyo# python -c 'import pyo'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/src/pyo/pyo/__init__.py", line 27, in <module>
from .lib import analysis as analysis
File "/usr/src/pyo/pyo/lib/analysis.py", line 32, in <module>
from ._core import *
File "/usr/src/pyo/pyo/lib/_core.py", line 58, in <module>
from .._pyo import *
ModuleNotFoundError: No module named 'pyo._pyo'
root@03b9f0f72677:/usr/src/pyo# cd ..
root@03b9f0f72677:/usr/src# python -c 'import pyo'
WxPython is not found for the current python version.
Pyo will use a minimal GUI toolkit written with Tkinter (if available).
This toolkit has limited functionnalities and is no more
maintained or updated. If you want to use all of pyo's
GUI features, you should install WxPython, available here:
http://www.wxpython.org/
Nice catch! Indeed, pyo.py (the python frontend) exists as a source file in the repo, but the backend part (the compiled library) is not there, only the C sources. So if you import pyo from the repo, it looks around to import the .so file and doesn't find it...
Hi,
I'm trying to compile pyo from source (so I can work on a patch).
I get an import error after following the instructions for 64 bit Linux:
This
Dockerfile
replicates the error: