By default, `FindPython` and its relatives will choose the newest Python version which is installed on the system. However, during Debian upgrades to a new Python release in the testing and unstable releases, the newest version will sometimes be partially broken, which can make CMake-driven builds less reliable. For this reason, I've carried a small Debian-specific patch in our CMake package for a while now, which queries the current Python default version with `py3versions --default --version` and prefers that version if none is requested. As far as I can tell, it works fine and causes no regressions, so I'm considering opening a merge request for this. As this addresses a relatively minor problem for a limited set of users, I wanted to ask for opinions first, though.