pip shim availability different by architecture?

[wlritchi]

I have two Linux machines, one x86_64 and one arm64. The software stack on each is broadly similar. I have installed pyenv 1.2.27 on both machines, and used it to install Python 3.9.4. The set of files installed in .pyenv/versions/3.9.4/bin is different depending on the architecture. In particular, the following binaries (plus versioned symlinks) exist only on the x86_64 machine:

• easy_install
• pip

Since 3.9.4 is the only version of Python installed via pyenv on either machine, pyenv on the arm64 machine does not create a shim for easy_install or pip. However, the system Python has a pip binary, and consequently, the system version of pip will be used, even inside a pyenv. This is understandable, but certainly unexpected for someone new to pyenv.

1. Is the difference in behaviour caused because the upstream Python downloads include different sets of binaries depending on the architecture?
2. Should pyenv try to do anything about this case, where the system Python includes a binary that's not present in any pyenv-managed Python version?