If you're just using python as a local scripting language, and not pushing production code, the other option is to simply not bother with any of this. When the

If you're just using python as a local scripting language, and not pushing production code, the other option is to simply not bother with any of this. When there's a new python version I'm interested in, I install it via Homebrew and update my zshrc to clobber everything else via $PATH. All my scripts and tools are broken? Just reinstall the packages globally. Whatever. Since the big 3.x transition, it's pretty rare for forwards-compatibility to break (IME), and if something does, I can just try running prior python3x binaries until I find the last version that worked. It's hideous, but honestly the least stressful way I've found to date.