开云体育

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*
<<< >>>/

Ahh this is turning out to be more tricky than I thought. I am using Linux
Mint 19.3 which uses python 3.6. It was no problem to load the dependencies
which I listed for python 3.6 but they would not work when I used them with
python 3.7 which although it looked in the right place for the
dist-packages it could not load them so I guess that there are significant
changes. Unfortunately I can't simply unload python 3.6 and upgrade to
python 3.7 as 3.6 is integrated into too many Mint packages and is really a
system file. I guess that I am stuck with nanoVNAsaver 0.2.1 for the next 2
or 3 years until a new Mint version brings a higher version of python or
unless I switch to another distro like Arch or openSuse which keep very
current.

I like Mint but don't like not progressing nanoVNAsaver.

73, Graeme ZL2APV

On 1/15/20 11:02 AM, Alberto I2PHD wrote:

Unfortunately apt-get does not know any of those....
I tried installing PyQt5, numpy, scipy and pyserial, but apt-get

declared those as unknown packages...

Probably they are part of a bigger package, but here I need the

advice of a Linux expert...


???? apt-get probably won't find them unless you use the exact name.?
Synaptic, on the other hand, probably will.? Is Synaptic available in
your distro?

On Thu, Jan 16, 2020 at 08:26 AM, Rune Broberg wrote:

I'm a little confused as to the decision on the Linux Mint packagers to
release 19.3 late last year with Python 3.6, when 3.7 was already more

than

18 months old, and 3.8 had just been released as well. Going with a

version

that old is bound to cause problems for the users.

Yes, we might even have got a newer version of python-pip3 - see below.

Anyway, getting near to the bottom of this now. Following notes apply to
LM19.3.

As I understand it

$ python3.7 -m pip install .

parses ~/nanovna-saver/requirements.txt and installs the latest versions
of the required python distribution packages if they are not already
installed i.e.

scipy
pyqt5
pyserial
numpy

pip will always install the latest versions, not whatever (older) versions
happen to be available from the distro package management system - which is
good.

Since 15.12.19 when I installed nanovna-saver-0.2.2a there have been two
new versions of PyQt5...



The installation error reported arises when pip3 attempts to install
PyQt5==5.14.1. We are not alone...



The pip3 version provided with the distro package python3-pip appears to
be too old.

$ pip3 -V
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)

Having read more about it seems that using sudo with pip3 to overcome the
error (as suggested in my earlier post #9634 and elsewhere) is a bad idea;
if you need to use sudo you are probably trying to modify a distro file.

There is no easy way to upgrade the version of pip3 supplied by the distro
package python3-pip. If the package manager advertises a new version then
you can install that as an update. It's a distro file and you shouldn't
try to upgrade it any other way. I managed to break (and fix) pip3 several
times in the attempt.

One way round this problem would be to install nanovna-saver in a python
virtual environment.

Another way is to modify ~/nanovna-saver/requirements.txt...

scipy
pyqt5==5.13.2
pyserial
numpy

then from ~/nanovna-saver/

$ python3.7 -m pip install -r ./requirements.txt .

This installs PyQt5==5.13.2 which is the version I used on 15.12.19.

I have tested this and it seems to work properly.

I do not understand why I had to explicitly specify the path to
requirements.txt though.

Nick