Closed sjoro closed 5 years ago
It looks like doing an absolute import will work around the problem
Temporary fix that seems to work:
1) rename io
under lmatools
as, e.g., lmaio
2) modify setup.py
by removing lmatools.io
from packages
3) run python setup.py install
4) copy the renamed lmaio
directory under the lmatools
installation path with the name io
I've reorganized the package structure to avoid this problem. @sjoro I think this problem is now fixed on the reorgpackage branch.
FYI, I ran into a similar issue to this when installing from source in Python 3.7. I fixed it locally by basically renaming the io directory to something else and changing all the relevant import statements. If the submodule directories were placed into a master lmatools directory (e.g., like glmtools does), would that help?
@tjlang this is what the branch mentioned in the above package was meant to do. Does installing from that branch fix the problem for you?
OK, @deeplycloudy, that fixed the install. Should that branch be made the master branch? It would make the package less confusing to install.
Thanks for the test. With that in mind, I went ahead with PR #24, and will close this issue.
Installation of
lmatool
results in an error. Apparently the installation gets a conflict with the pythonio
-module.