[chirp_devel] Is anyone running chirp on Python 3?

Fri Jun 24 08:09:50 PDT 2022

There is a GitHub repo that is parallel to the Mercurial repo. (They are
mirrors of each other.) Several of us have contributed via that repo, to
both Python 2 and Python 3 trees.

https://github.com/kk7ds/chirp

In my opinion, the lack of direction is the most significant obstacle to
making further progress. A few of us have made contributions to the py3
tree, but there are places in which the originally intended direction is
unclear. One example is how live mode radios should work. An experiment was
initiated in the code base, but is incomplete, and the author is unclear as
to whether it is the right path. Someone would need to step up and take the
reins of a design spec to steer the project. That's a significant effort,
and I don't think anyone has been ready to do that (including Chirp's
creator, as far as I can tell).

Once a direction is set, and a design is in place, I think there are
probably enough of us who could finish what's been started. However, right
now, things are rather piecemeal with respect to contributions to the py3
tree.

You mentioned building new things. I suspect a number of us have
contemplated that. However, there is an enormous amount of work and
knowledge built into the Chirp codebase, and especially into the drivers
for the huge number of supported radios. Any "new things" that might take
over from Chirp would either need to build all of that again from scratch
(not practical) or essentially adopt the Chirp driver design and "just"
build a new UI over that. Which, in essence, is what the py3 tree is, with
a wxPython GUI replacing what's there in Python 2.

Nick's idea of a to-do list is a good one, if those of us who've had a go
with the py3 tree each chip in our findings and build up a collective set
of thoughts. However, my feeling is that we really need some input from Dan
to help with direction, and an expression of his thoughts and ideas of
where Chirp should be going and how it might get there. Any contributions
we make need to go through Dan to get into the main Chirp repo (as opposed
to a fork), so his input really is key.

My 2 cents.

Martin.
KD6YAM

On Fri, Jun 24, 2022 at 7:43 AM Leam Hall via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

>  From a "new guy" perspective, I see two major questions. First, using
> mercurial is a barrier since a lot of developers are on GitHub or GitLab.
> The Chirp Developer page has a lot of info, so that should be doable. I'm
> not sure if the Gmail from Mercurial instructions are up to date, since
> Gmail has borked...err...changed their stuff yet again.
>
> The other question, and maybe I'm reading between the wrong lines, is that
> there's a sense of "meh". Python 3 has been out for a while; Joe mentioned
> the lack of direction, Nick isn't confident that it's worth the effort to
> document the needs. What's the general feeling about continuing as is or
> building to new things?
>
> Leam
>
> On 6/24/22 09:33, Dominick C. Pastore via chirp_devel wrote:
> > It seems like we get a question about the status of the Python 3
> conversion and what work is left every month or two. I wonder if it would
> be useful to put together some sort of Py3 TODO list, both for people who
> are curious and for people who want to help but don't know where it's
> needed. I'm not sure how much work that would be to put together, or if it
> would be worth it.
> >
> > Nick
> >
> > On Fri, Jun 24, 2022, at 9:10 AM, Joe Pizzi via chirp_devel wrote:
> >> The challenge, in my opinion, is that not only is it changing from
> Python 2
> >> to Python 3, but it is changing from gtk to wxPython, because gtk also
> had
> >> some incompatible change.
> >>
> >> Joe Pizzi
> >>
> >> -----Original Message-----
> >> From: chirp_devel-bounces at intrepid.danplanet.com
> >> <chirp_devel-bounces at intrepid.danplanet.com> On Behalf Of Leam Hall via
> >> chirp_devel
> >> Sent: Friday, June 24, 2022 6:39 AM
> >> To: chirp_devel at intrepid.danplanet.com
> >> Subject: Re: [chirp_devel] Is anyone running chirp on Python 3?
> >>
> >> Hey all,
> >>
> >> I don't mean to sound like a know it all; I'm pretty sure I know very
> >> little. It looks like the project is still active, and folks are
> >> contributing. A local used it to load up my radio yesterday, I'm
> new-ish to
> >> the area and still had the old repeaters programmed in. Pretty sure my
> >> little Baofeng can't reach half way across the country, to the old
> >> repeaters. *sigh*
> >>
> >> What's the challenge with moving to Python 3? What is holding things at
> >> Python 2?
> >>
> >> Leam
> >>
> >>
> >> On 6/23/22 20:44, Joe Pizzi wrote:
> >>> Lack of time, focus, direction. At least on my part.
> >>>
> >>> Joe Pizzi
> >>>
> >>> -----Original Message-----
> >>> From: chirp_devel-bounces at intrepid.danplanet.com
> >>> <chirp_devel-bounces at intrepid.danplanet.com> On Behalf Of Leam Hall
> via
> >>> chirp_devel
> >>> Sent: Thursday, June 23, 2022 8:08 PM
> >>> To: chirp_devel at intrepid.danplanet.com
> >>> Subject: Re: [chirp_devel] Is anyone running chirp on Python 3?
> >>>
> >>> Hey Joe,
> >>>
> >>> Is the "not complete" due to lack of time, or...? I can do some
> Python, if
> >>> that helps.
> >>>
> >>> Leam
> >>>
> >>>
> >>> On 6/23/22 19:07, Joe Pizzi wrote:
> >>>> There is a python 3 branch that fixes those kinds of errors. It is not
> >>>> complete, however.
> >>>>
> >>>> Joe Pizzi
> >>>>
> >>>> -----Original Message-----
> >>>> From: chirp_devel-bounces at intrepid.danplanet.com
> >>>> <chirp_devel-bounces at intrepid.danplanet.com> On Behalf Of Leam Hall
> via
> >>>> chirp_devel
> >>>> Sent: Thursday, June 23, 2022 5:50 AM
> >>>> To: chirp_devel at intrepid.danplanet.com
> >>>> Subject: [chirp_devel] Is anyone running chirp on Python 3?
> >>>>
> >>>> I'm getting a lot of syntax errors on "except Exception, e:" and
> issues
> >>> with
> >>>> print statements. Running Python 3.10 on Void Linux.
> >>>>
> >>>> Thanks!
> >>>>
> >>>> Leam
> >>>
> >>
> >> --
> >> Automation Engineer        (reuel.net/resume)
> >> Scribe: The Domici War     (domiciwar.net)
> >> General Ne'er-do-well      (github.com/LeamHall)
> >> _______________________________________________
> >> chirp_devel mailing list
> >> chirp_devel at intrepid.danplanet.com
> >> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> >> Developer docs:
> http://chirp.danplanet.com/projects/chirp/wiki/Developers
> >>
> >> _______________________________________________
> >> chirp_devel mailing list
> >> chirp_devel at intrepid.danplanet.com
> >> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> >> Developer docs:
> http://chirp.danplanet.com/projects/chirp/wiki/Developers
> > _______________________________________________
> > chirp_devel mailing list
> > chirp_devel at intrepid.danplanet.com
> > http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> > Developer docs:
> http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
> --
> Automation Engineer        (reuel.net/resume)
> Scribe: The Domici War     (domiciwar.net)
> General Ne'er-do-well      (github.com/LeamHall)
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20220624/cb0aa4f8/attachment-0001.html 