CHIRP

# About CHIRP-next

This page explains the chirp-next build, why it is necessary, what to expect, and how you can help.

## Why is this necessary?

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). 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. Further, the developers of PyGTK decided to mothball the project and **not ever** move to support Python 3. 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. 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.

Mac and Linux users are likely painfully aware of the increasing difficulty in running CHIRP that has been creeping up for the last few years. Python 2.7 was officially End-of-Lifed in 2020, and many Linux distros dropped support around then. Apple held on a little longer, but has removed Python 2.7 from MacOS now. Windows' users have been largely unaffected directly by the deprecation issue, but developers have an increasingly shrinking set of platforms they can use to continue CHIRP development.