[chirp_users] Moving Chirp Daily to python3?
mfncooper at gmail.com
Sun Jun 6 15:08:02 PDT 2021
> The "move" includes two changes, from what I understand, because Python3
> no longer has the PyGTK interface? So, you cannot move from Python2 to
> Python3 and keep the existing GUI.
There is pygtkcompat, which "makes it possible to focus on porting to Gtk
3.x while not changing anything else, users and developers can keep on
using the software as before". My reading on that (I have not used it)
suggests that keeping the existing GUI is entirely possible. Then, once
Chirp is on Python 3, any move to wxWidgets can be addressed on its own
merits, rather than being embedded as part of a Python 3 port.
Of the tests that get executed by the "run_tests.py" script, I have all
> tests passing with the exception of Yaesu FTM-3200D R. I expect I can get
> that passing before next week.
Have you been able to test against any live-mode radios? They don't have
tests included in the run_tests.py suite. Testing against at least one or
two (for example, at least one Icom and one Kenwood) would seem pretty
important as a part of validating the move.
Don't get me wrong - if you're willing to take on the task of getting the
Python 3 move up and running, which you clearly are, more power to you, and
kudos for taking it on. I'm just personally not interested in futzing
around with a Python 2+3 codebase or switching GUI technology when I see
neither as necessary.
> What would be the next steps? I can see that there might be radio updates
> since the branch. Should I merge the updated radio files into my branch and
> make sure that works? Or, should we get the GUI up to speed? When I ran the
> GUI, I noticed several features not yet there.
> Joe Pizzi
> On 6/4/2021 11:10 AM, Martin Cooper wrote:
> On Wed, Jun 2, 2021 at 8:47 PM Mark Schoonover via chirp_users <
> chirp_users at intrepid.danplanet.com> wrote:
>> Python2 has been EOL for 18 months. This also means any Python modules
>> are probably no longer being maintained. I would guess moving chirp to
>> Python3 would be quite the endeavor as well.
> In my opinion, a move to Python 3 would be great, but is being hampered by
> two things, at least based on what is in the 'py3' branch:
> * The "move" to Python 3 isn't really a move; the code is being updated in
> such a way as to preserve Python 2 compatibility.
> * At the same time as moving to Python 3, the UI technology is being
> switched from Gtk to wxPython.
> If it was just a straight *move* to Python 3, dropping Python 2 and
> allowing developers to take full advantage of Python 3 features, I, and I
> suspect others, would be more interested in helping out, since I don't
> honestly see much point in keeping Python 2 compatibility any more. As you
> say, it's been EOL for a while.
> Also, I feel that switching the UI technology should be a separate effort
> from updating the language version, unless there's some compelling reason
> that the two cannot be done sequentially. I'd say get to Python 3 first,
> and then maybe think about switching UI technologies.
> My 2 cents.
> chirp_users mailing listchirp_users at intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Joe Pizzi at pizzi.joe at gmail.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
> Joe Pizzi
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> This message was sent to Martin Cooper at mfncooper at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users