Coming from pyenv
A pyenv alternative that doesn't compile Python
Last checked 17 November 2026
In short: pyenv builds most Python versions from source on your Mac, so it needs a compiler and a set of Homebrew libraries first. Termhint installs prebuilt CPython from python-build-standalone, checks each download's checksum and GitHub attestation, and switches versions from the .python-version files you already have. It is a paid Mac app that also manages Node, Ruby, Go, Java, Xcode and more (all languages). If you need PyPy, several Pythons active at once, or your own build flags, keep pyenv.
How pyenv works
- Built from source. "Most Pyenv-provided Python releases are source releases and are built from source as part of installation." Before the first install, the README asks you to install Python's build dependencies.
- Build dependencies on macOS. The pyenv wiki suggests the Xcode Command Line Tools, Homebrew, and
brew install openssl@3 openssl readline sqlite3 xz tcl-tk@8 libb2 zstd zlib pkgconfig. It warns that compilation can fail on unmet system dependencies, or succeed and give a Python with odd failures at runtime. - Shims. pyenv puts a folder of shims first on
PATH, one for every Python command across your versions. Runningpipruns the shim, which hands the command to pyenv to pick the version. - Shell setup.
pyenv init --installadds setup code to your shell startup files. - Version choice.
PYENV_VERSION, then.python-versionin the folder or a parent, then the globalversionfile. A.python-versionmay list several versions, one per line, all active at once. - Many distributions. CPython, PyPy, Stackless, Jython and more.
- No virtualenv management. The README leaves that to
virtualenvor thepyenv-virtualenvplugin.
From pyenv's README and its wiki (suggested build environment) on 17 November 2026.
What changes with Termhint
| pyenv | Termhint | |
|---|---|---|
| Install | Downloads the source and compiles it | Downloads a prebuilt CPython from python-build-standalone; nothing is compiled |
| Before the first install | Xcode Command Line Tools and Homebrew libraries | Nothing |
| How the version is chosen | Shims on PATH | No shims: the shell puts the folder's version first on PATH as you change folders |
| Version files | .python-version (several versions allowed) | .python-version (first version used), .tool-versions |
| Distributions | CPython, PyPy, Stackless, Jython and more | CPython |
| Virtual environments | Not managed (plugin available) | Not created or managed; the prompt can show the active one |
| Platforms | macOS, Linux; Windows through WSL or the pyenv-win fork | macOS 14+ on Apple silicon |
| Price | Free, open source | Paid after a 7-day trial |
pyenv column: pyenv README, 17 November 2026.
Your .python-version files keep working
Termhint walks up from the current folder and uses the nearest .python-version, or the python line of a .tool-versions. It reads the first version in the file and skips comments. A prefix such as 3.13 means the newest 3.13 you installed. The file is read as data and never run.
$ cat .python-version
# for the API
3.12.4
3.11
$ termhint runtime current
python 3.12.4 not installed (/Users/you/api/.python-version)
If a folder asks for a Python you don't have, the shell prints one line with the install command; nothing installs on cd. Both zsh and bash switch.
The pyenv commands you know
| pyenv | Termhint |
|---|---|
pyenv install 3.13 | termhint runtime install python 3.13 |
pyenv install -l | termhint runtime list-remote python |
pyenv versions | termhint runtime list python |
pyenv local 3.12 | termhint runtime use python 3.12 (writes .tool-versions) |
pyenv global 3.13 | termhint runtime use -g python 3.13 |
pyenv shell 3.11 | export TERMHINT_PYTHON_VERSION=3.11 |
pyenv exec python script.py | termhint runtime exec python@3.12 -- python3 script.py |
pyenv uninstall 3.11.9 | termhint runtime uninstall python 3.11.9 |
Editors and GUI apps can point at ~/.local/share/termhint/runtimes/python/default.
Virtual environments
Termhint does not create or manage virtual environments. Make them the usual way, for example python3 -m venv .venv with the Python that Termhint installed. If you use a Termhint prompt theme, the prompt can show the active environment's name (termhint settings set prompt.venv.on on, on by default; see prompt themes).
Leaving pyenv
termhint runtime migrate pyenv --dry-run # the plan: versions, pip tools, lines to turn off
termhint runtime migrate pyenv # do it
termhint runtime migrate --undo # turn pyenv's lines back on, byte for byte
- Each Python version you have in pyenv is downloaded again as a prebuilt, checked build. Nothing is copied from pyenv's folders.
- pyenv's global version becomes Termhint's default.
- Tools you installed with pip that have commands are reinstalled into the matching Termhint version with
python3 -m pip install. - pyenv's lines in
~/.zshrc,~/.zprofile,~/.bash_profile,~/.bashrcand~/.profileare backed up, then turned off with#termhint-off#in front. - Removing pyenv is a separate choice (
--remove):brew uninstallif Homebrew installed it, and its folders go to the Trash, only once every version installed and every tool moved.
A version pyenv has that python-build-standalone doesn't publish, such as a PyPy build, is not installed, and pyenv stays on if its default can't be installed. The same steps are a button in Settings → Runtimes → Other Managers.
Keep pyenv if…
- You need PyPy, Jython or another distribution. Termhint installs CPython only.
- You run several Pythons at once, for example for tox, from one
.python-version. Termhint uses the first version in the file. - You build Python with your own options, such as
PYTHON_CONFIGURE_OPTS="--enable-framework". Termhint never compiles. - You use pyenv-virtualenv and like how it ties environments to folders.
- You also work on Linux, Windows or an Intel Mac, or in fish. Termhint is for Apple-silicon Macs on macOS 14 or later, in zsh and bash.
- You want free and open source.
What it costs
Every feature works for 7 days with no account and no card. After that, a one-time license: $11.99 for 1 Mac, $19.99 for 3, $29.99 for 5 (pricing). The same license covers Node and the other languages, autocomplete and prompt themes. Python versions you installed keep working if the license lapses.
Termhint is not affiliated with pyenv, python-build-standalone or the Python Software Foundation.