There are various shims and hacks for temporary compatibility that we could have (and in some cases, did) explore, but the end result was the same: something had to change. This left CHIRP in a tough spot, as moving to Python 3 not only required significant changes to almost every radio driver (of which there are about 350) and basically a complete re-write of the GUI at the same time. Further, the developers of PyGTK decided to mothball the project and not ever move to support Python 3. Since then, the Python development team defined Python 3.0, which is an evolution of the language, but with many incompatible changes, specifically in the areas that affect CHIRP. When CHIRP started in 2008, it was based on two core pieces of modern-at-the-time software, Python 2.x (the language) and PyGTK (the GUI toolkit). This page explains the chirp-next build, why it is necessary, what to expect, and how you can help.ĭownload the latest CHIRP-next build here Why is this necessary? ¶
The CHIRP project is working on a major project to re-write some of the core components necessary for longevity in the years to come. What are the system requirements for CHIRP-next?.What if my radio does not work in CHIRP-next yet?.
