native-api
native-api
I apologize for taking long to review. I looked at this soon after you made it, had doubts about it and thought that perhaps I can allocate time to make...
CC @tastyfrankfurt @git1e @kirkzhangtech @grepwood @nauni77
This is Pyenv-Sync's problem. As per [PEP 394](https://peps.python.org/pep-0394/), custom Python environments are expected to provide the `python` command. It's Pyenv-Sync's job to ensure that whatever it adds under `$(pyenv root)/versions`...
> Depending on a distribution or system configuration, `python` may or may not be installed. This phrase in the PEP refers to the default, system-provided Python. Pyenv-managed installations are not...
In fact, as a corollary of the PEP, we cannot, in the general case, use an executable name other than `python` -- because nothing else is guaranteed to exist! While...
Pyenv-managed installations are activated environments. You explicitly activate them by selecting a version to use other than `system`.
The fact that the activation process looks different doesn't matter -- the principle and the net effect are the same.
As per the documentation, completions are supposed to be installed via `eval "$(pyenv init -)"`. The path is given as an explanation and is correct for a git clone installation....
Cannot reproduce in either Ubuntu 22.04.1 or Kubuntu 22.04.5 .
``` config.status: creating pyconfig.h config.status: pyconfig.h is unchanged ``` Looks like you have some leftovers from a previous failed build. Please clear them out from TMPDIR: ``` rm -rf $TMPDIR/python-build.*...