<div dir="ltr"><div dir="ltr">On Sat, Sep 21, 2019 at 7:15 AM Barry Jackson <<a href="mailto:zen25000@zen.co.uk">zen25000@zen.co.uk</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> From: <a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a> <<a href="mailto:chirp_users-bounces@intrepid.danplanet.com" target="_blank">chirp_users-bounces@intrepid.danplanet.com</a>> on behalf of Nicolas Pike <<a href="mailto:nicolas@jetblackjelly.com" target="_blank">nicolas@jetblackjelly.com</a>><br>
> Sent: Tuesday, September 17, 2019 8:07:29 AM<br>
> To: <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a> <<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>><br>
> Subject: [chirp_users] CHIRP on py3<br>
> <br>
> I see there is a py3 branch. What is the state of CHIRP on Python 3?<br>
> I am intending to further improve the FT70 driver, and a pal as an FT3 which he has done some outline memory mapping work for.<br>
> Should we be developing against the py3 branch?<br>
> Thanks.<br>
> Nicolas<br>
<br>
As distros are now dropping Py2 surely this is a must.<br>
<br>
I maintain the chirp package for Mageia and we have already dropped Py2 <br>
in our development branch for the next release.<br></blockquote><div><br></div><div>I maintain chirp for Fedora and it will not work as of Fedora 31 which is now in Beta.</div><div><br></div><div>There has been a lot of work but I'm not sure what the exact status is, however, you can track it here:<br><br></div><div><a href="https://chirp.danplanet.com/issues/495">https://chirp.danplanet.com/issues/495</a></div><div><br></div><div>Thanks,</div><div>Richard</div><div>KF5OIMÂ </div></div></div>