I've done a bulk build to assess what's needed to move the default py3 version to 3.8. Various Linux distros are using Python 3.8 already and I think even LTS are moving to it so fallout is mostly already fixed upstream. (3.7 is now on "security fixes only").
I've committed fixes for some minor fallout that can be done pre switch, some others are simpler to fix at the time of switching which I've fixed locally, here are the remaining ones - if anyone can help out with getting these ports updated/fixed that would be appreciated. There may be some runtime fallout too but it's very unlikely we'll find that until we switch. This is a good time in the release cycle to make this move so there's enough time to find and fix before OpenBSD 6.8! www/seamonkey Could not find gconf-2.0 -> seems repeatable but I don't understand why py3 would be involved so maybe it's fallout from something else graphics/vulkan-tools 'time' has no attribute 'clock' -> port is outdated; this was fixed as part of larger commit (looks like it was in 1.1.119), https://github.com/KhronosGroup/Vulkan-Tools/commit/6a0ba2cdd textproc/libxmlbird TypeError -> comes from cloudpickle used by py-doit used by libxmlbird. -> cloudpickle needs updating to at least 1.1.1 (some newer versions break py2 but I think that will be ok, ports depending on it are py3) sysutils/salt cannot import name 'linux_distribution' from 'platform' -> https://github.com/saltstack/salt/issues/55310 -> "no longer referenced in Salt code as of the upcoming 3001 (Sodium) release" -> probably fixed with https://github.com/saltstack/salt/commit/fe075aaace
