Open shinjoe opened 6 years ago
Update: initial error fixed after pip -U pytest
.
New issue:
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests\test_initialize.py:1: in <module>
from hardware import logger, u, log_file, log_filename
E ModuleNotFoundError: No module named 'hardware'
Hmm... I thought it was listed in requirements.txt
I think in some versions of pytest, you run pytest
and in other versions you run py.test
...
just tried pytest
; yields the same complaint about E ModuleNotFoundError: No module named 'hardware'
I probably need to stipulate that you need to run the setup.py
first
for hardware to work....
I'm investigating getting everything registered with PyPi first. But I need to pick a clever name that doesn't conflict with anything else that already exists there....
Maybe diglab.hardware?
On 13 Jul 2018, at 17:02, shinjoe wrote:
Update: initial error fixed after
pip -U pytest
.New issue:
Hint: make sure your test modules/packages have valid Python names. Traceback: tests\test_initialize.py:1: in <module> from hardware import logger, u, log_file, log_filename E ModuleNotFoundError: No module named 'hardware'
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jondoesntgit/hardware/issues/19#issuecomment-404982358
oh right, that makes sense. Sure, sounds good; no rush.
That namespace sounds fine to me.
Did I miss a step?
oh, looks like a hidden dependency?