Imports blow up in pystache
matthewdeanmartin opened this issue · comments
Matthew Martin commented
matth@lenovo MINGW64 ~/GitHub/no_algo_twitter (main)
$ pycco src/*.py
Traceback (most recent call last):
File "C:\Users\matth\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\matth\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\Scripts\pycco.exe\__main__.py", line 4, in <module>
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\__init__.py", line 1, in <module>
from .main import * # noqa
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\main.py", line 60, in <module>
from pycco.generate_index import generate_index
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\generate_index.py", line 9, in <module>
from pycco_resources import pycco_template
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco_resources\__init__.py", line 1, in <module>
import pystache
File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pystache\__init__.py", line 2, in <module>
from init import *
ModuleNotFoundError: No module named 'init'
matth@lenovo MINGW64 ~/GitHub/no_algo_twitter (main)
$ python --version
Python 3.8.7
I think it is blowing up on some really old school import syntax. I don't remember seeing that sort of import that omits the package name since python 2.
There is some motion to take over pystache ref: pypi/support#1422 and we could see new releases of pystache, but in the meanwhile, pycco seems to be broken in a lot of venvs.