Hi Greg,

I don't normally advocate for working on forks of code but I have seen at least 3 or 4 people now ask the same question so maybe we could get together on github.com where we could send pull requests and work "locally" until the mercurial repo is in better shape. Alex Page has a fork of chirp with some baseline changes to the source files using the 2to3 conversion helper script bundled with python3 at https://github.com/atpage/chirp

Also, there is a different mailing list, chirp_devel, where chirp development is discussed.

Tony.

From: chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Greg Shuflin via chirp_users <chirp_users@intrepid.danplanet.com>
Sent: Friday, September 4, 2020 7:42 AM
To: chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com>
Subject: [chirp_users] Python 3 port

Hi, I'm a relatively new user of Chirp. I like the software and I'm interested in contributing to porting it to Python3. I notice that there's a py3 branch that hasn't had any new commits since February. I spend some time trying to get that branch to run on my system without success, and I'm not sure if it's expected to work in either Python2 or Python3 at this point. In any case, what's the best way to contribute to moving it to Python3?

Sent with ProtonMail Secure Email.