[chirp_devel] Python 3 is *still* not supported?

[Martin Cooper]

To correct one point from the embedded e-mail: while the original source
control system is Mercurial, there is a parallel tree on GitHub.

https://github.com/kk7ds/chirp

A number of people, including myself, have contributed to Chirp via GitHub,
on both master and py3 branches. All changes go both ways, so developers
are free to choose which source control system they prefer.

I think one of the main sticking points to a complete Python 3 version of
Chirp is the GUI. With the py3 branch, Chirp is moving to wxPython
(wxWidgets), and really, nobody has stepped up to do significant work on
that. A start has been made for clone-mode radios, but when I looked into
it with a live-mode radio some time ago, it seemed to me that there were
design ideas in place, but not enough hints to pick those up and run with
them - at least not for someone largely unfamiliar with wxPython, like me.
There also seemed to be some other design changes to the way the GUI works
that are probably not directly related to wxPython.

A decent amount of the py3 codebase does work, though. For example, I got
to the point where I can use chirpc (the CLI version) to read and write
memories with my live-mode radio. So the core functionality is there, for
at least some drivers. (I know a few other folks have worked on drivers for
their specific radios too.)

Martin.
KD6YAM

On Mon, Apr 18, 2022 at 3:10 PM Barry Jackson via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> On 13/04/2022 18:04, James Keener wrote:
> > This has been brought up multiple times over the years. There is a
> python 3 branch and multiple people, including myself, have offered to do
> work but there's no real drive from the project owner to make the
> transition and it's difficult to ensure the updated gui code and all of the
> radio interfaces work 100% correctly.
> >
> > The project owner seems to think that packaging it with python 2 in a
> snap package is acceptable.
> >
> > Jim
>
> It is a shame that this project has effectively died as far as it's
> inclusion in linux distros is concerned because py2 is dead.
> I received a direct mail as a result of my post. I am not disclosing the
> sender but I think it deserves to be seen.
> ----------------
>
> "Hi Barry,
>
> Just saw your note on the Chirp email list. Wow, no support of Python 3.
>
> I have been meaning to get involved with the project as would be a good
> way for me to contribute. Python 2.x? Puhlease.
>
> Looking at the one response though, am not surprised. Was "amused" that
> they use a source control system that is not git. Didn't want to spend
> the time coming up to speed on that (archaic?) system so never pursued.
> Looks like I will be unsubscribing from the list now as there is nothing
> that I contribute.
>
> Thank you bringing this up."
>
> ----------------
>
> Seems that people would be willing to help if only there was the will to
> move forward.
>
> Barry
> G4MKT
> _______________________________________________
> 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/20220418/5f2ef781/attachment-0001.html