native-api

MacOS uses Zsh as its default shell. Look in `~/.zshrc`.

Then look where it's set in your shell startup files. The following command makes Bash that `$SHELL` points to trace executing its startup files (lots of output!): ``` PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}():...

See https://github.com/pyenv/pyenv/blob/master/plugins/python-build/README.md#package-download-mirrors on how to make a mirror for Pyenv downloads.

> A quick fix would be to add this line: > > ```shell > if [[ $1 == "python" && $2 == "-m" && $3 == "pip" ]]; then >...

Since running `pyenv rehash` won't break anything if run unnecessarily, I guess we can just look for "`-m pip`" in `$*`.

Most probably, either you didn't [set up your shell](https://github.com/pyenv/pyenv/blob/master/README.md#b-set-up-your-shell-environment-for-pyenv), or something is in front of `$(pyenv root)/shims` in `PATH` and overrides them.

Need the diagnostic information as per [the issue template](https://github.com/pyenv/pyenv/blob/master/.github/ISSUE_TEMPLATE.md) to be able to say anything more specific.

WFM on a Hackintosh VM: ``` % \time -h pyenv --version pyenv 2.3.0-11-ge676fde9 0,19s real 0,03s user 0,07s sys % \time -h pyenv --help Usage: pyenv [] 1,60s real 0,22s...

My blind guesses are an antivirus, including Apple's built-in one (other users have already reported it disrupting Pyenv operation), or your Bash runs in Rosetta.

> I did notice most of the time is apparently spent waiting on threads That's not too surprising. It's probably waiting for subprocesses -- Bash code is very fork-heavy. Okay,...