Pyenv is not a "common tool". It's used by a very small minority of devs since:

- it's used only by dev, and half of the python coders are not devs

- it works only on unix. Most people install python on windows (https://discuss.python.org/t/python-download-stats-for-may-2..., and that doesn't take in consideration anaconda or the appstore). Unless you count the obscure fork used by even less people.

- And yet on mac, if they don't use the official installer, they use mostly brew, not pyenv. On Linux, the officials repos or things like deadnsnake or epel. And of course docker. Pyenv is a tiny fractions of that, because any alternative solution is better known and easier.

- hard to use because it compiles things, fails easily in non obvious ways and assume you manage the path correctly, so it's really, really, popular only with people that want to deal with that. In fact the setups instructions are huge: https://github.com/pyenv/pyenv#how-it-works

- that's just what we see in the field. I go to a lot of different shops every years because I'm a freelancers, and I encountered pyenv twice in 10 years.

> That it happens to compile under the hood is an implementation detail that users may not even be aware off.

Of course not. The setup docs themself tell you to "Install Python build dependencies before attempting to install a new Python version.".

So not only you have to be aware of it, but you must be capable of setting up a compilation environment, and if you fail to do so, it will not work.

pyenv is not standard python. It's not "a common tool". It's a tool for a niche of specialists with domain specific knowledge.

Yeah well that just means mindlessly copy pasting a command into your terminal before moving onto the next step in the installation instructions. But now that I read what the command does, it turns out it does install sqlite so yeah..