[chirp_users] Moving Chirp Daily to python3?
I hope this is the right place to ask this.
Is there a timeline for getting Chirp-daily working on python3?
73's
KE6RTV
Mark
It doesn't seem to be a priority. Is there really any desparate need?
On 02/06/2021 21:51 Mark Coulter mark@coulter.org wrote:
I hope this is the right place to ask this.
Is there a timeline for getting Chirp-daily working on python3?
73's
KE6RTV
Mark
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-971-0366 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
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.
On Wed, Jun 2, 2021, 19:21 Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:
It doesn't seem to be a priority. Is there really any desparate need?
On 02/06/2021 21:51 Mark Coulter mark@coulter.org wrote:
I hope this is the right place to ask this.
Is there a timeline for getting Chirp-daily working on python3?
73's
KE6RTV
Mark
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-971-0366 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Mark Schoonover - KA6WKE at mark@ka6wke.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jun 2, 2021 at 8:47 PM Mark Schoonover via chirp_users < chirp_users@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.
Martin. KD6YAM
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.
I guess we could change the GUI from PyGTK to wxPython, and then change from Python2 to Python3, but that means even longer before it is ready.
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.
Dan,
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 KI5LST
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@intrepid.danplanet.com mailto:chirp_users@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.
Martin. KD6YAM
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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.
Martin. KD6YAM
Dan,
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 KI5LST 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@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.
Martin. KD6YAM
chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Joe Pizzi
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
Hello Everyone,
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.
I have to disagree here.. Python2 is over. It's dead and it's going to get harder and harder to get it installed on newer operating systems. It really is a mess but it's happened and we just have to push forward with Python3. Without it and a newer GUI widget set, we're going to loose this excellent (and free) tool to program our various radios.
--David KI6ZHD
I only have two Baofeng UV-5Rs.
Therefore, I cannot test anything else.
If having to test on web every radio is a prerequisite, it will never get done.
Are there more tests that we have, to verify functioning?
Taking the remainder of the conversation to the developer list.
Joe Pizzi KI5LST
On Sun, Jun 6, 2021, 5:09 PM Martin Cooper mfncooper@gmail.com wrote:
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.
Martin. KD6YAM
Dan,
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 KI5LST 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@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.
Martin. KD6YAM
chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- Joe Pizzi
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 list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I'm working on it.
I have most tests passing. The gui is still not as full featured as the python version, but I've procreate my radios with it.
Do you have an immediate need for the ported version?
Joe Pizzi KI5LST
On Wed, Jun 2, 2021, 8:52 PM Mark Coulter mark@coulter.org wrote:
I hope this is the right place to ask this.
Is there a timeline for getting Chirp-daily working on python3?
73's
KE6RTV
Mark
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
You procreate w/your radios? That's dedication! :)
73! Mark KA6WKE Youtube: https://www.youtube.com/ka6wke Website: https://www.ka6wke.net
On Fri, Jun 4, 2021 at 8:23 AM Joe Pizzi pizzi.joe@gmail.com wrote:
I'm working on it.
I have most tests passing. The gui is still not as full featured as the python version, but I've procreate my radios with it.
Do you have an immediate need for the ported version?
Joe Pizzi KI5LST
On Wed, Jun 2, 2021, 8:52 PM Mark Coulter mark@coulter.org wrote:
I hope this is the right place to ask this.
Is there a timeline for getting Chirp-daily working on python3?
73's
KE6RTV
Mark
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com 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 Mark Schoonover - KA6WKE at mark@ka6wke.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Don't you just love AutoIncorrect?
Joe KI5LST
On 6/4/2021 10:26 AM, Mark Schoonover via chirp_users wrote:
You procreate w/your radios? That's dedication! :)
73! Mark KA6WKE Youtube: https://www.youtube.com/ka6wke https://www.youtube.com/ka6wke Website: https://www.ka6wke.net https://www.ka6wke.net
On Fri, Jun 4, 2021 at 8:23 AM Joe Pizzi <pizzi.joe@gmail.com mailto:pizzi.joe@gmail.com> wrote:
I'm working on it. I have most tests passing. The gui is still not as full featured as the python version, but I've procreate my radios with it. Do you have an immediate need for the ported version? Joe Pizzi KI5LST On Wed, Jun 2, 2021, 8:52 PM Mark Coulter <mark@coulter.org <mailto:mark@coulter.org>> wrote: I hope this is the right place to ask this. Is there a timeline for getting Chirp-daily working on python3? 73's KE6RTV Mark _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Joe Pizzi at pizzi.joe@gmail.com <mailto:pizzi.joe@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 <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Mark Schoonover - KA6WKE at mark@ka6wke.net <mailto:mark@ka6wke.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 http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Pizzi at pizzi.joe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (6)
-
David Ranch -
Joe Pizzi -
Mark Coulter -
Mark Schoonover -
Martin Cooper -
Nigel A. Gunn G8IFF/W8IFF