adding frequencies with chirp

________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of chirp_users-request@intrepid.danplanet.com chirp_users-request@intrepid.danplanet.com Sent: Friday, May 15, 2020 2:00 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: chirp_users Digest, Vol 137, Issue 13

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. Re: chirp_users Digest, Vol 137, Issue 12 (IT1 Stuart Blake Tener, USNR) 2. Re: Yaesu FT-8500 (W Paul Mills) 3. Re: Yaesu FT-8500 (Nigel A. Gunn G8IFF/W8IFF) 4. Re: Yaesu FT-8500 (Nigel A. Gunn G8IFF/W8IFF)

----------------------------------------------------------------------

Message: 1 Date: Thu, 14 May 2020 15:31:13 -0400 From: "IT1 Stuart Blake Tener, USNR" stuart.tener@bh90210.net Subject: Re: [chirp_users] chirp_users Digest, Vol 137, Issue 12 To: chirp_users@intrepid.danplanet.com Message-ID: 20200514153113.Horde.-Zn2TpRTN4d2IcjKv7IKjge@mgtmail.com Content-Type: text/plain; charset="utf-8"

Nolan,

Indeed you might be thinking that you are reminding people of some obvious piece of wisdom to conduct a search for old articles, but indeed this is a fools errand (unless you are suggesting such messages were very recent in the last 30 to 45 days, which I did not get the impression you were).

Why you ask?

Python is still under heavy development and unless these older messages specifically substantiate what the exact version of Python existed at the time the messages were written and what specific Python version they were referring to, their content and meaning may be entirely inapplicable now as perhaps the technical concerns at issue at the time may well have been overcome my changes to the Python language or been amended in the current instantiation of the Chirp source code base. In either event, we would not gain such insights from old messages. Thus, obviously asking what the issues are now is a very different question from "what were the issues then?", a question I did not ask and therefore had no need to research the answer for.

Secondly, you can't agree with me that "Python 3 would be nice to have", because I did not say that. I meant to assert in the most compelling manner that I could articulate that the idea of moving to Python3 is an imperative and to not do so terribly disadvantages users and retards the security of a system they are expected to continue to keep Python2 running upon.

Let me clear here, I appreciate all the hard work that Dan, et alia, have put into Chirp and mean in no way to diminish the excellence of that work or to suggest any lack of appreciation. Moreover, if the argument is "We can't move to Python2 because its a part time project and nobody has time." I understand and accept that fully. However, that in no way changes the fact that distributing software in a now virtually unsupported language instigates a very high risk for the users of that software in such a case. Moving to Python3 is something that must happen, just as many programs written for Amateur Radio are no longer used because they ran on TRS-80s and Apple IIs, and we don't use that technology anymore. Chirp will eventually move in such a direction if it is not ported to Python3 soon (or some other secure language) as people that care about the security posture of their systems will be loath to remain to keep an environment running that is not longer be actively patched with security patches and having bugs remediated there within.

73,

Stuart, N3GWG ?