On 8/24/21 12:16 AM, Peter Vollan wrote:
I did everything you said. Now, how do I get it to run?
Update from Mint 17.3 to 20.2
or
Read that error message and dig into the mcomm code and find the spot
where some function id being handed a string data type when it wants a
bytes data type, and modify the code as necessary to essentially
backport mcomm to the older version of python and pyserial.
Ok you may think I was joking or being inconsiderate, but in fact that
is the sincere advice, not only in general, but specifically to address
this problem.
Last time you said this:
https://www.mail-archive.com/[email protected]/msg14268.html
That shows 3 things:
1: You did somehow get python 3.5 installed.
2: That did get you past your original error. (it just ran into some
other error next)
3: mcomm ended up loading some files from
/usr/lib/python3/
and some files from
/usr/lib/python3.5/
Those two directories might be the same (python3 might be a symlink to
python3.5), or they might be different. The python3 directory might be
full of python-3.4 files.
It *looks* like the program ended up loading files from two different
versions of python. But even if both paths were really 3.5, the next
step is still the same anyway...
The error message looks like an error in the mcomm code, but since I
don't have any such error on an even newer version of python, that
suggests the code is fine, it just needs some newer version of python
than 3.5. Definitely 3.8.6 is ok, but probably there is some version
between 3.5. and 3.8.6 where it starts working.
You could try searching for newer python packages to install, but no one
is going to have python from today compiled for mint from 5 years ago. I
just spent a few minutes looking and didn't find anything. But I don't
use Mint myself so I don't know all the likely places to look. Can you
just install debian or ubuntu packages on mint? I don't know but I would
not assume that.
You could try building python from source. The directions are actually
short and simple, it might "just work", but I wouldn't hold my breath on
that. ;)
I have no idea where you can find a newer version of python for mint
17.3. mint 20.2 yes, 17.3? no idea. But you can get a current python for
the current mint no problem.
You could try the newer mint from a live usb thumb drive without
actually installing just to see if it will actually resolve the problem.
Other options, maybe pyenv ? I've never used it, but people suggest it
as a way to run different versions of python
https://github.com/pyenv/pyenv/wiki
I do not recommend it. I recommend update your OS to current.
--
bkw
On Mon, 23 Aug 2021 at 18:23, Daryl Tester
<[email protected]
<mailto:[email protected]>> wrote:
Peter, I responded to this earlier this month. To quote:
> Earlier, Peter Vollan wrote:
>
>> Do I have the wrong type of Python? I run Mint 17.3.
>
> According to the interwebz, default Python for Mint 17.3 is
Python 3.4, and the traceback
> "SyntaxError: can use starred expression only as assignment
target" is specific to
> < Python 3.5, so yeah, you'll need to get a later version. See:
>
<https://stackoverflow.com/questions/34372731/installing-python-3-5-on-linux-mint-17-3
<https://stackoverflow.com/questions/34372731/installing-python-3-5-on-linux-mint-17-3>>
> This does mean you'll need to invoke your script specifically
with "python3.5 ...".
On 24/8/21 10:11 am, Peter Vollan wrote:
> When I invoke mcomm with "mcomm" at the command line, it calls
the following script:
>
> #!/usr/bin/python3
> """ Launch mcomm
> """
> import subprocess
> import sys
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
*sys.argv[1:]])
>
> ...which yields the following error message:
>
> File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
*sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>
> Sorry to bother everyone with this, I'm sure it is something
simple about python. My python3 is 3.4.3
>
