Somebody wrote:
======================================================
/However if I just do this into a clean directory...//
//
//$ git clone
//$ python3.7 ./nanovna-saver/nanovna-saver.py//
//
//then nanovna-saver runs fine, with no "python3.7 -m pip install ."/
======================================================
Oh, I wish that would work also for Debian Buster....? but it doesn't....
This is a screen capture of what happens when I give those commands :
db@debian:~$ git clone
Cloning into 'nanovna-saver'...
remote: Enumerating objects: 39, done.
remote: Counting objects: 100% (39/39), done.
remote: Compressing objects: 100% (29/29), done.
remote: Total 2684 (delta 19), reused 20 (delta 10), pack-reused 2645
Receiving objects: 100% (2684/2684), 1.96 MiB | 2.66 MiB/s, done.
Resolving deltas: 100% (1882/1882), done.
adb@debian:~$ python3.7 ./nanovna-saver/nanovna-saver.py
Traceback (most recent call last):
? File "./nanovna-saver/nanovna-saver.py", line 17, in <module>
??? from NanoVNASaver.__main__ import main
? File "/home/adb/nanovna-saver/NanoVNASaver/__main__.py", line 23, in <module>
??? from .NanoVNASaver import NanoVNASaver
? File "/home/adb/nanovna-saver/NanoVNASaver/NanoVNASaver.py", line 23, in <module>
??? import numpy as np
ModuleNotFoundError: No module named 'numpy'
adb@debian:~$
======================================================
:-(
--
/*73 Alberto I2PHD*
<<< >>>/
Alberto I2PHD