[chirp_devel] chirp-py3 status?

[James Keener]

I've used the current py3 branch with a UV5R.

Jim

On Wed, Dec 9, 2020 at 10:14 AM Matthew Poletiek via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> Thanks for the response Charlie.
>
> I didn't even notice the import dialogues weren't working. Would be nice
> to be able to import from RepeaterBook as well. I'll take a harder look at
> this over the holidays and see what I can do.
>
> One man will never be able to test all the drivers, but we can definitely
> knock off the BF-F8HP off the list. I assume this covers a lot of other
> Baofeng HT's as well.
>
> I'll keep submitting patches to py3, but I'll also be maintaining my own
> version locally and on github for now.
>
> -------------------------------------------
> Matthew Poletiek
> 303.810.9082
> matthew.poletiek at gmail.com
> www.matthewpoletiek.com
>
>
>
>
> On Wed, Dec 9, 2020 at 12:35 AM Charlie Li <ml+CHIRP at vishwin.info> wrote:
>
>> Matthew Poletiek via chirp_devel wrote:
>> > Anyone know what the current status of the py3 branch is?
>> >
>> There was a small thread last month on this mailing list about it. A
>> quote from Dan himself:
>> > You're welcome to send me patches against the py3 branch if you want
>> (please make them obvious), but I have to prioritize fixes and stuff on the
>> main branch just out of respect to the 99.9% of users that it impacts.
>>
>> tl;dr Dan's too busy to bother and he deems Flatpak good enough (at
>> least for Linux folks). Additionally, the amount of work and changes
>> needed cannot really be broken down into smaller commits that won't
>> break the build or runtime in the meantime, at least not conceptually.
>> > Gentoo Linux has dropped this package from it's main repo due to lack of
>> > movement, but I cloned this branch, made a few adjustments
>> > (https://chirp.danplanet.com/issues/8475
>> > <https://chirp.danplanet.com/issues/8475>) and everything seemed to
>> work
>> > great!
>> >
>> So has FreeBSD ports, in the quest to remove everything Python 2-only
>> (chiefly for CHIRP, pygtk2) before Python 2 itself gets removed by the
>> end of this month/year. Spoiler: I contributed the last update before it
>> was removed, despite another pending update I submitted based on the
>> existing py3 branch. Said pending update is only a stopgap, however.
>> > I'm assuming it's a few driver iterations behind the main branch, but it
>> > would be really nice to get py3 moving since Python2 is practically
>> EOL'ed.
>> >
>> It's more than a few driver iterations behind. Drivers are *the* sore
>> point in fully realising Python 3 support. Converting them to work in
>> Python 3 (apart from correcting syntax that would otherwise preclude
>> CHIRP from launching at all) involves far more than running 2to3.
>>
>> Although there's a rudimentary wxPython 4 GUI in the py3 branch, it's
>> really incomplete compared to using pygobject's pygtk shim. And even
>> that has some issues with certain dialogs not working (import and export
>> come to mind), but at least it's better than wxPython 4 right now.
>>
>> --
>> Charlie Li
>> K3CL
>>
>> (This email address is for mailing list use only; replace local-part
>> with vishwin for off-list communication)
>>
> _______________________________________________
> 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/20201209/08b4899f/attachment-0001.html