Curious if the chirp software works with the BJ-318 model? I see there was some question some time ago about it but not sure if resolved or reply. There seems tobe compatibility with BJ-218 model. Anyone know?
 
Steve Rish


-----Original Message-----
From: chirp_users-request@intrepid.danplanet.com
Sent: Sun, 19 Jul 2020 12:00:02 -0700
To: chirp_users@intrepid.danplanet.com
Subject: chirp_users Digest, Vol 139, Issue 8

Send chirp_users mailing list submissions to
chirp_users@intrepid.danplanet.com

To subscribe or unsubscribe via the World Wide Web, visit
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
or, via email, send a message with subject or body 'help' to
chirp_users-request@intrepid.danplanet.com

You can reach the person managing the list at
chirp_users-owner@intrepid.danplanet.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of chirp_users digest..."


Today's Topics:

1. Newest Chirp doesn't seem to work with Python 2.6.6 --
invalid syntax on the anytone778uv.py driver (David Ranch)
2. Re: Newest Chirp doesn't seem to work with Python 2.6.6 --
invalid syntax on the anytone778uv.py driver (Martin Cooper)
3. Re: Newest Chirp doesn't seem to work with Python 2.6.6 --
invalid syntax on the anytone778uv.py driver (David Ranch)
4. Error using CHIRP with my AnyTone AT778-UV (Tony Moriarty)
5. Re: Error using CHIRP with my AnyTone AT778-UV (Jim Unroe)
6. Re: Error using CHIRP with my AnyTone AT778-UV (Tony Moriarty)
7. Re: Newest Chirp doesn't seem to work with Python 2.6.6 --
invalid syntax on the anytone778uv.py driver (Martin Cooper)
8. Re: Newest Chirp doesn't seem to work with Python 2.6.6 --
invalid syntax on the anytone778uv.py driver
(Nigel A. Gunn G8IFF/W8IFF)




Message: 1
Date: Sat, 18 Jul 2020 19:17:16 -0700
From: David Ranch <chirp@trinnet.net>
Subject: [chirp_users] Newest Chirp doesn't seem to work with Python
2.6.6 -- invalid syntax on the anytone778uv.py driver
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID: <d748ca57-7fbc-3f3e-5fb9-fedd3623db2d@trinnet.net>
Content-Type: text/plain; charset="utf-8"


Hello Everyone,

I've been a happy Chirp user for a long time but haven't upgraded for
some time. I was previously running the TIP version back from Feb 3
2018 (chirp-hg-e3b90fa8c316) and that worked well but once I fetched the
newest version with:

wget http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz

Both of these newest versions give me the below errors:

lrwxrwxrwx 1 dranch dranch 21 Jul 18 19:09 chirp-tip-newest ->
chirp-hg-37a6a6d6f425
lrwxrwxrwx 1 dranch dranch 21 Jul 12 13:22 chirp-tip-newest ->
chirp-hg-061e53a8a2cc


The errors I'm seeing are:
--
$ ./chirpw
Traceback (most recent call last):
File "./chirpw", line 24, in <module>
from chirp.drivers import *
File
"/home/archive/Chirp/chirp-hg-37a6a6d6f425/chirp/drivers/anytone778uv.py",
line 192
for val in TONE_MAP_VAL_TO_TONE}
^
SyntaxError: invalid syntax
--

It was mentioned by Jim Unroe to install the "future" pip package but
installing version 0.18.2 didn't help. Any thoughts?

--David
KI6ZHD
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200718/505736d3/attachment-0001.html



Message: 2
Date: Sat, 18 Jul 2020 21:39:08 -0700
From: Martin Cooper <mfncooper@gmail.com>
Subject: Re: [chirp_users] Newest Chirp doesn't seem to work with
Python 2.6.6 -- invalid syntax on the anytone778uv.py driver
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
<CAGEtHi+8XXu-kD8+Mwsw0qye82Kj88Tuj9q481GXtmCeD4p62g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi David,

Chirp is written for Python 2.7, which is why you're seeing the error.
Dictionary comprehensions were introduced with 2.7. It's possible that
you're just unlucky in trying to use a driver that uses a 2.7 feature, but
given that 2.7 is the target version, it's also quite possible that you'd
run into more problems if you worked around this one. (If you wanted to
try, google for dictionary comprehensions in 2.6, but don't be too
surprised if you hit something else shortly thereafter.)

That 2.7 is the target platform isn't well documented. There's a note in
the wiki for a Win32 dev env that says "chirp is currently written for
Python 2.7 and above", though in the same para it also says it "will
generally run on Python 2.6.x". That latter likely depends on the features
you want to use. The KK7DS Python runtime for Mac OSX, needed for Chirp on
a Mac, is also a packaging of Python 2.7.

Martin.
KD6YAM

On Sat, Jul 18, 2020 at 7:18 PM David Ranch <chirp@trinnet.net> wrote:

>
> Hello Everyone,
>
> I've been a happy Chirp user for a long time but haven't upgraded for some
> time. I was previously running the TIP version back from Feb 3 2018
> (chirp-hg-e3b90fa8c316) and that worked well but once I fetched the newest
> version with:
>
> wget http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz
>
> Both of these newest versions give me the below errors:
>
> lrwxrwxrwx 1 dranch dranch 21 Jul 18 19:09 chirp-tip-newest ->
> chirp-hg-37a6a6d6f425
> lrwxrwxrwx 1 dranch dranch 21 Jul 12 13:22 chirp-tip-newest ->
> chirp-hg-061e53a8a2cc
>
>
> The errors I'm seeing are:
> --
> $ ./chirpw
> Traceback (most recent call last):
> File "./chirpw", line 24, in <module>
> from chirp.drivers import *
> File
> "/home/archive/Chirp/chirp-hg-37a6a6d6f425/chirp/drivers/anytone778uv.py",
> line 192
> for val in TONE_MAP_VAL_TO_TONE}
> ^
> SyntaxError: invalid syntax
> --
>
> It was mentioned by Jim Unroe to install the "future" pip package but
> installing version 0.18.2 didn't help. Any thoughts?
>
> --David
> KI6ZHD
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Martin Cooper at mfncooper@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200718/33227491/attachment-0001.html



Message: 3
Date: Sat, 18 Jul 2020 22:35:31 -0700
From: David Ranch <chirp@trinnet.net>
Subject: Re: [chirp_users] Newest Chirp doesn't seem to work with
Python 2.6.6 -- invalid syntax on the anytone778uv.py driver
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID: <e2101fa6-1852-4a01-460f-ab7f5ad82b15@trinnet.net>
Content-Type: text/plain; charset="windows-1252"


Hey Martin,

Good to hear from you! Hmmm.. I'm using Centos6 here and it does have
an option to put Python27 on to the side so I guess I can give that a
try. It's just strange to me that certain drivers would use Python2.7
syntax but others would be fine with 2.6 syntax. I must say, this lack
of backwards compatibility that Python has continued to show
(especially) through it's various Python3 generations is frustrating!

Thanks for the tip and I'll report back what I see.

--David
KI6ZHD


On 07/18/2020 09:39 PM, Martin Cooper wrote:
> Hi David,
>
> Chirp is written for Python 2.7, which is why you're seeing the error.
> Dictionary comprehensions were introduced with 2.7. It's possible that
> you're just unlucky in trying to use a driver that uses a 2.7 feature,
> but given that 2.7 is the target version, it's also quite possible
> that you'd run into more problems if you worked around this one. (If
> you wanted to try, google for dictionary comprehensions in 2.6, but
> don't be too surprised if you hit something else shortly thereafter.)
>
> That 2.7 is the target platform isn't well documented. There's a note
> in the wiki for a Win32 dev env that says "chirp is currently written
> for Python 2.7 and above", though in the same para it also says it
> "will generally run on Python 2.6.x". That latter likely depends on
> the features you want to use. The KK7DS Python runtime for Mac OSX,
> needed for Chirp on a Mac, is also a packaging of Python 2.7.
>
> Martin.
> KD6YAM
>
> On Sat, Jul 18, 2020 at 7:18 PM David Ranch <chirp@trinnet.net
> <mailto:chirp@trinnet.net>> wrote:
>
>
> Hello Everyone,
>
> I've been a happy Chirp user for a long time but haven't upgraded
> for some time. I was previously running the TIP version back from
> Feb 3 2018 (chirp-hg-e3b90fa8c316) and that worked well but once
> I fetched the newest version with:
>
> wget http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz
>
> Both of these newest versions give me the below errors:
>
> lrwxrwxrwx 1 dranch dranch 21 Jul 18 19:09 chirp-tip-newest
> -> chirp-hg-37a6a6d6f425
> lrwxrwxrwx 1 dranch dranch 21 Jul 12 13:22
> chirp-tip-newest -> chirp-hg-061e53a8a2cc
>
>
> The errors I'm seeing are:
> --
> $ ./chirpw
> Traceback (most recent call last):
> File "./chirpw", line 24, in <module>
> from chirp.drivers import *
> File
> "/home/archive/Chirp/chirp-hg-37a6a6d6f425/chirp/drivers/anytone778uv.py",
> line 192
> for val in TONE_MAP_VAL_TO_TONE}
> ^
> SyntaxError: invalid syntax
> --
>
> It was mentioned by Jim Unroe to install the "future" pip package
> but installing version 0.18.2 didn't help. Any thoughts?
>
> --David
> KI6ZHD
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> <mailto:chirp_users@intrepid.danplanet.com>
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Martin Cooper at mfncooper@gmail.com
> <mailto:mfncooper@gmail.com>
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
> <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to David Ranch at chirp@trinnet.net
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200718/fa50c098/attachment-0001.html



Message: 4
Date: Sun, 19 Jul 2020 09:38:05 +0100
From: Tony Moriarty <boris.bandit@gmail.com>
Subject: [chirp_users] Error using CHIRP with my AnyTone AT778-UV
To: chirp_users@intrepid.danplanet.com
Message-ID:
<CAPYnjKPzbN9ShP80sJFqrk5P-exMqi9Am9kf+5EHV4XwuVRsUg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi.

Firstly, although I've used Chirp for years, this is the first time I've
used this forum - please be patient with me!

I was delighted to discover recently that Chirp now supports the Anytone
778-UV - I've had one for a while, and the "other" software available for
it was rather limited.

Anyway, having downloaded the latest daily build and attempted to read the
radio, I'm getting an error message that includes the text :

"Radio version not in allowed list for AnyTone-778UV: 000: 49 41 54 37 37
38 55 56 IAT778UV

008: 01 56 31 30 30 00 00 06 .V100..."

It appears that Chirp is correctly interacting with the radio via the
relevant com port, but doesn't like what the radio tells it.

Since there doesn't seem to have been a rash of issues raised on this
subject, I didn't want to raise it as a bug report till I'd made enquiries
here.

My PC runs an up-to-date installation of Windows 10

The debug file includes the following (I've chopped out lines that don't
seem relevant!):

[2020-07-19 08:50:02,053] chirp.logger - DEBUG: CHIRP daily-20200718 on
WinVista/7 (Python 2.7.10)

.

.

.

[2020-07-19 08:50:02,224] chirp.directory - INFO: Registered AnyTone_778UV
= AnyTone778UV

[2020-07-19 08:50:02,224] chirp.directory - INFO: Registered Retevis_RT95 =
RetevisRT95

[2020-07-19 08:50:02,224] chirp.directory - INFO: Registered CRT_Micron_UV
= CRTMicronUV


[2020-07-19 08:50:02,397] chirp.directory - INFO: Registered
Vertex_Standard_VXA-700 = VXA700Radio

[2020-07-19 08:50:02,397] elib.intl - DEBUG: Set environment variable
'LANG' to 'en_GB' ('kernel32.SetEnvironmentVariableW')

[2020-07-19 08:50:02,397] elib.intl - DEBUG: Set environment variable
'LANG' to 'en_GB' ('msvcrt._putenv')

[2020-07-19 08:50:02,397] elib.intl - DEBUG: Set environment variable
'LANG' to 'en_GB' ('msvcr90._putenv')

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.mainapp - INFO: Skipping existing stock
config

[2020-07-19 08:50:02,928] chirp.ui.reporting - DEBUG: Checking for updates

[2020-07-19 08:50:03,351] chirp.ui.reporting - DEBUG: Server reports
version daily-20200718 is latest

[2020-07-19 08:50:14,335] chirp.ui.mainapp - DEBUG: User selected AnyTone
778UV on port COM3

[2020-07-19 08:50:14,430] chirp.ui.clone - DEBUG: Clone thread started

[2020-07-19 08:50:14,944] chirp.drivers.anytone778uv - DEBUG: entered
program mode

[2020-07-19 08:50:15,444] chirp.drivers.anytone778uv - DEBUG: ver_response
=

[2020-07-19 08:50:15,444] chirp.drivers.anytone778uv - DEBUG: 000: 49 41 54
37 37 38 55 56 IAT778UV

008: 01 56 31 30 30 00 00 06 .V100...


[2020-07-19 08:50:15,444] chirp.drivers.anytone778uv - DEBUG: radio model:
'AT778UV' version: 'V100'

[2020-07-19 08:50:15,444] chirp.drivers.anytone778uv - DEBUG: allowed_types
= {'AT778UV': ['V200']}

[2020-07-19 08:50:15,444] chirp.drivers.anytone778uv - DEBUG: model in
allowed_types

[2020-07-19 08:50:15,944] chirp.ui.reporting - DEBUG: Reporting exception

[2020-07-19 08:50:15,944] chirp.ui.common - ERROR: -- Exception: --

[2020-07-19 08:50:15,944] chirp.ui.common - ERROR: Traceback (most recent
call last):

File "chirp\ui\clone.pyo", line 256, in run

File "chirp\drivers\anytone778uv.pyo", line 569, in sync_in

File "chirp\drivers\anytone778uv.pyo", line 371, in do_download

RadioError: Radio version not in allowed list for AnyTone-778UV: 000: 49 41
54 37 37 38 55 56 IAT778UV

008: 01 56 31 30 30 00 00 06 .V100...



[2020-07-19 08:50:15,944] chirp.ui.common - ERROR: ----------------

[2020-07-19 08:50:15,944] chirp.ui.clone - ERROR: Clone failed: Radio
version not in allowed list for AnyTone-778UV: 000: 49 41 54 37 37 38 55 56
IAT778UV

008: 01 56 31 30 30 00 00 06 .V100...


[2020-07-19 08:50:16,007] chirp.ui.clone - DEBUG: Clone thread ended

[2020-07-19 08:50:16,007] chirp.ui.reporting - DEBUG: Reporting model
usage: AnyTone_778UV,download,True

[2020-07-19 08:50:16,007] chirp.ui.reporting - DEBUG: Reporting exception

[2020-07-19 08:50:16,007] chirp.ui.inputdialog - ERROR: --- Exception
Dialog: Radio version not in allowed list for AnyTone-778UV: 000: 49 41 54
37 37 38 55 56 IAT778UV

008: 01 56 31 30 30 00 00 06 .V100...

---

[2020-07-19 08:50:16,007] chirp.ui.inputdialog - ERROR: Traceback (most
recent call last):

File "chirpw", line 68, in <module>

AttributeError: 'NoneType' object has no attribute 'split'


[2020-07-19 08:50:16,007] chirp.ui.inputdialog - ERROR:




I'm happy to provide more info if needed.

Can anyone suggest a way forward, please?

All the best,

Tony Moriarty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200719/4755247d/attachment-0001.html



Message: 5
Date: Sun, 19 Jul 2020 06:56:18 -0400
From: Jim Unroe <rock.unroe@gmail.com>
Subject: Re: [chirp_users] Error using CHIRP with my AnyTone AT778-UV
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
<CADnO8U6AppvMJQ2kNx-=ovC397W_Fp50V97YsWqxo2aDTJvVGg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Hi Tony,

On Sun, Jul 19, 2020 at 4:40 AM Tony Moriarty <boris.bandit@gmail.com> wrote:

> Anyway, having downloaded the latest daily build and attempted to read the radio, I'm getting an error message that includes the text :
>
> "Radio version not in allowed list for AnyTone-778UV: 000: 49 41 54 37 37 38 55 56 IAT778UV
>
> 008: 01 56 31 30 30 00 00 06 .V100..."
>

Your radio is reporting "V100" and CHIRP currently expects it to be
"V200". I would submit a bug report with the same information that you
provided here so the additional version can be added to the driver for
the AT-778UV.

Jim KC9HI




Message: 6
Date: Sun, 19 Jul 2020 13:04:04 +0100
From: Tony Moriarty <boris.bandit@gmail.com>
Subject: Re: [chirp_users] Error using CHIRP with my AnyTone AT778-UV
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
<CAPYnjKOFPZyUsMeY2COhVfB16vuQQuOyzkUnbPn27T=QYW0beA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Jim,

Many thanks for the advice - I'll do as you suggest.

Cheers,

Tony M G4TRY


On Sun, 19 Jul 2020 at 11:58, Jim Unroe <rock.unroe@gmail.com> wrote:

> Hi Tony,
>
> On Sun, Jul 19, 2020 at 4:40 AM Tony Moriarty <boris.bandit@gmail.com>
> wrote:
>
> > Anyway, having downloaded the latest daily build and attempted to read
> the radio, I'm getting an error message that includes the text :
> >
> > "Radio version not in allowed list for AnyTone-778UV: 000: 49 41 54 37
> 37 38 55 56 IAT778UV
> >
> > 008: 01 56 31 30 30 00 00 06 .V100..."
> >
>
> Your radio is reporting "V100" and CHIRP currently expects it to be
> "V200". I would submit a bug report with the same information that you
> provided here so the additional version can be added to the driver for
> the AT-778UV.
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Tony Moriarty at boris.bandit@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200719/6f47ed86/attachment-0001.html



Message: 7
Date: Sun, 19 Jul 2020 08:26:54 -0700
From: Martin Cooper <mfncooper@gmail.com>
Subject: Re: [chirp_users] Newest Chirp doesn't seem to work with
Python 2.6.6 -- invalid syntax on the anytone778uv.py driver
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID:
<CAGEtHi+e5JtLevbBQqE2ubKTW5F1n6z4O2EN5N9SWVSRLkseLg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Sat, Jul 18, 2020 at 10:37 PM David Ranch <chirp@trinnet.net> wrote:

> It's just strange to me that certain drivers would use Python2.7 syntax
> but others would be fine with 2.6 syntax.
>

Not really. As I mentioned, Chirp is targeted at Python 2.7. All Python
2.6.x syntax is valid in 2.7, but 2.7 adds some new capabilities. It's not
strange that someone would want to take advantage of those new capabilities
when they're available as part of the target version.

This is not really different from someone working in C++. If the target
version was C++11, any code written for C++98 or C++03 would still be fine,
but there are new features - and new syntax - that can be taken advantage
of in C++11 to make life simpler / more robust. Code written using those
new features may not compile with an older compiler.

Also, I'll note in passing that Python 2.7 was released 10 years ago, and
security updates for Python 2.6.6 were stopped 7 years ago, in 2013.

Martin.
KD6YAM



> --David
> KI6ZHD
>
>
> On 07/18/2020 09:39 PM, Martin Cooper wrote:
>
> Hi David,
>
> Chirp is written for Python 2.7, which is why you're seeing the error.
> Dictionary comprehensions were introduced with 2.7. It's possible that
> you're just unlucky in trying to use a driver that uses a 2.7 feature, but
> given that 2.7 is the target version, it's also quite possible that you'd
> run into more problems if you worked around this one. (If you wanted to
> try, google for dictionary comprehensions in 2.6, but don't be too
> surprised if you hit something else shortly thereafter.)
>
> That 2.7 is the target platform isn't well documented. There's a note in
> the wiki for a Win32 dev env that says "chirp is currently written for
> Python 2.7 and above", though in the same para it also says it "will
> generally run on Python 2.6.x". That latter likely depends on the features
> you want to use. The KK7DS Python runtime for Mac OSX, needed for Chirp on
> a Mac, is also a packaging of Python 2.7.
>
> Martin.
> KD6YAM
>
> On Sat, Jul 18, 2020 at 7:18 PM David Ranch <chirp@trinnet.net> wrote:
>
>>
>> Hello Everyone,
>>
>> I've been a happy Chirp user for a long time but haven't upgraded for
>> some time. I was previously running the TIP version back from Feb 3 2018
>> (chirp-hg-e3b90fa8c316) and that worked well but once I fetched the newest
>> version with:
>>
>> wget http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz
>>
>> Both of these newest versions give me the below errors:
>>
>> lrwxrwxrwx 1 dranch dranch 21 Jul 18 19:09 chirp-tip-newest
>> -> chirp-hg-37a6a6d6f425
>> lrwxrwxrwx 1 dranch dranch 21 Jul 12 13:22 chirp-tip-newest
>> -> chirp-hg-061e53a8a2cc
>>
>>
>> The errors I'm seeing are:
>> --
>> $ ./chirpw
>> Traceback (most recent call last):
>> File "./chirpw", line 24, in <module>
>> from chirp.drivers import *
>> File
>> "/home/archive/Chirp/chirp-hg-37a6a6d6f425/chirp/drivers/anytone778uv.py",
>> line 192
>> for val in TONE_MAP_VAL_TO_TONE}
>> ^
>> SyntaxError: invalid syntax
>> --
>>
>> It was mentioned by Jim Unroe to install the "future" pip package but
>> installing version 0.18.2 didn't help. Any thoughts?
>>
>> --David
>> KI6ZHD
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Martin Cooper at mfncooper@gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe@intrepid.danplanet.com
>
>
>
> _______________________________________________
> chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to David Ranch at chirp@trinnet.net
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Martin Cooper at mfncooper@gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200719/d28a58fd/attachment-0001.html



Message: 8
Date: Sun, 19 Jul 2020 11:47:14 -0400 (EDT)
From: "Nigel A. Gunn G8IFF/W8IFF" <nigel@ngunn.net>
Subject: Re: [chirp_users] Newest Chirp doesn't seem to work with
Python 2.6.6 -- invalid syntax on the anytone778uv.py driver
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID: <1501298602.334912.1595173634688@email.ionos.com>
Content-Type: text/plain; charset="utf-8"

Nothing to stop you installing 2.6, 27. and 3.something to ensure compatibility. They will all reside together.
All available from python.org for free download.


> On 19 July 2020 at 11:26 Martin Cooper <mfncooper@gmail.com> wrote:
>
>
>
> On Sat, Jul 18, 2020 at 10:37 PM David Ranch < chirp@trinnet.net mailto:chirp@trinnet.net > wrote:
>
> > > It's just strange to me that certain drivers would use Python2.7 syntax but others would be fine with 2.6 syntax.
> >
> > >
> Not really. As I mentioned, Chirp is targeted at Python 2.7. All Python 2.6.x syntax is valid in 2.7, but 2.7 adds some new capabilities. It's not strange that someone would want to take advantage of those new capabilities when they're available as part of the target version.
>
> This is not really different from someone working in C++. If the target version was C++11, any code written for C++98 or C++03 would still be fine, but there are new features - and new syntax - that can be taken advantage of in C++11 to make life simpler / more robust. Code written using those new features may not compile with an older compiler.
>
> Also, I'll note in passing that Python 2.7 was released 10 years ago, and security updates for Python 2.6.6 were stopped 7 years ago, in 2013.
>
> Martin.
> KD6YAM
>
>
>
> > > --David
> > KI6ZHD
> >
> >
> > On 07/18/2020 09:39 PM, Martin Cooper wrote:
> >
> > > > > Hi David,
> > >
> > > Chirp is written for Python 2.7, which is why you're seeing the error. Dictionary comprehensions were introduced with 2.7. It's possible that you're just unlucky in trying to use a driver that uses a 2.7 feature, but given that 2.7 is the target version, it's also quite possible that you'd run into more problems if you worked around this one. (If you wanted to try, google for dictionary comprehensions in 2.6, but don't be too surprised if you hit something else shortly thereafter.)
> > >
> > > That 2.7 is the target platform isn't well documented. There's a note in the wiki for a Win32 dev env that says " chirp is currently written for Python 2.7 and above", though in the same para it also says it "will generally run on Python 2.6.x". That latter likely depends on the features you want to use. The KK7DS Python runtime for Mac OSX, needed for Chirp on a Mac, is also a packaging of Python 2.7.
> > >
> > > Martin.
> > > KD6YAM
> > >
> > > On Sat, Jul 18, 2020 at 7:18 PM David Ranch < chirp@trinnet.net mailto:chirp@trinnet.net > wrote:
> > >
> > > > > > >
> > > > Hello Everyone,
> > > >
> > > > I've been a happy Chirp user for a long time but haven't upgraded for some time. I was previously running the TIP version back from Feb 3 2018 (chirp-hg-e3b90fa8c316) and that worked well but once I fetched the newest version with:
> > > >
> > > > wget http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz
> > > >
> > > > Both of these newest versions give me the below errors:
> > > >
> > > > lrwxrwxrwx 1 dranch dranch 21 Jul 18 19:09 chirp-tip-newest -> chirp-hg-37a6a6d6f425
> > > > lrwxrwxrwx 1 dranch dranch 21 Jul 12 13:22 chirp-tip-newest -> chirp-hg-061e53a8a2cc
> > > >
> > > >
> > > > The errors I'm seeing are:
> > > > --
> > > > $ ./chirpw
> > > > Traceback (most recent call last):
> > > > File "./chirpw", line 24, in <module>
> > > > from chirp.drivers import *
> > > > File "/home/archive/Chirp/chirp-hg-37a6a6d6f425/chirp/drivers/anytone778uv.py", line 192
> > > > for val in TONE_MAP_VAL_TO_TONE}
> > > > ^
> > > > SyntaxError: invalid syntax
> > > > --
> > > >
> > > > It was mentioned by Jim Unroe to install the "future" pip package but installing version 0.18.2 didn't help. Any thoughts?
> > > >
> > > > --David
> > > > KI6ZHD
> > > > _______________________________________________
> > > > chirp_users mailing list
> > > > chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
> > > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> > > > This message was sent to Martin Cooper at mfncooper@gmail.com mailto:mfncooper@gmail.com
> > > > To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
> > > >
> > > > > > >
> > >
> > >
> > > _______________________________________________
> > > chirp_users mailing list
> > > chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
> > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> > > This message was sent to David Ranch at chirp@trinnet.net mailto:chirp@trinnet.net
> > > To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
> > >
> > > > > _______________________________________________
> > chirp_users mailing list
> > chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> > This message was sent to Martin Cooper at mfncooper@gmail.com mailto:mfncooper@gmail.com
> > To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
> >
> > > _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
>



Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1 937 825 5032
Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20200719/43e0659a/attachment-0001.html



_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

End of chirp_users Digest, Vol 139, Issue 8
*******************************************