<div dir="ltr"><div>Thanks for the response Charlie.</div><div><br></div><div>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. <br></div><div><br></div><div>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. </div><div><br></div><div>I'll keep submitting patches to py3, but I'll also be maintaining my own version locally and on github for now. <br></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>-------------------------------------------<br></div><div>Matthew Poletiek</div><div>303.810.9082</div><div><a href="mailto:matthew.poletiek@gmail.com" target="_blank">matthew.poletiek@gmail.com</a></div><div><a href="http://www.matthewpoletiek.com" target="_blank">www.matthewpoletiek.com</a></div><div><br></div><div><br></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 9, 2020 at 12:35 AM Charlie Li <<a href="mailto:ml%2BCHIRP@vishwin.info">ml+CHIRP@vishwin.info</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Matthew Poletiek via chirp_devel wrote:<br>
> Anyone know what the current status of the py3 branch is?<br>
> <br>
There was a small thread last month on this mailing list about it. A<br>
quote from Dan himself:<br>
> 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.<br>
<br>
tl;dr Dan's too busy to bother and he deems Flatpak good enough (at<br>
least for Linux folks). Additionally, the amount of work and changes<br>
needed cannot really be broken down into smaller commits that won't<br>
break the build or runtime in the meantime, at least not conceptually.<br>
> Gentoo Linux has dropped this package from it's main repo due to lack of<br>
> movement, but I cloned this branch, made a few adjustments<br>
> (<a href="https://chirp.danplanet.com/issues/8475" rel="noreferrer" target="_blank">https://chirp.danplanet.com/issues/8475</a><br>
> <<a href="https://chirp.danplanet.com/issues/8475" rel="noreferrer" target="_blank">https://chirp.danplanet.com/issues/8475</a>>) and everything seemed to work<br>
> great!<br>
> <br>
So has FreeBSD ports, in the quest to remove everything Python 2-only<br>
(chiefly for CHIRP, pygtk2) before Python 2 itself gets removed by the<br>
end of this month/year. Spoiler: I contributed the last update before it<br>
was removed, despite another pending update I submitted based on the<br>
existing py3 branch. Said pending update is only a stopgap, however.<br>
> I'm assuming it's a few driver iterations behind the main branch, but it<br>
> would be really nice to get py3 moving since Python2 is practically EOL'ed.<br>
> <br>
It's more than a few driver iterations behind. Drivers are *the* sore<br>
point in fully realising Python 3 support. Converting them to work in<br>
Python 3 (apart from correcting syntax that would otherwise preclude<br>
CHIRP from launching at all) involves far more than running 2to3.<br>
<br>
Although there's a rudimentary wxPython 4 GUI in the py3 branch, it's<br>
really incomplete compared to using pygobject's pygtk shim. And even<br>
that has some issues with certain dialogs not working (import and export<br>
come to mind), but at least it's better than wxPython 4 right now.<br>
<br>
-- <br>
Charlie Li<br>
K3CL<br>
<br>
(This email address is for mailing list use only; replace local-part<br>
with vishwin for off-list communication)<br>
</blockquote></div>