native-api

> However, when we have only one patch version installed, I don't see how does this apply here. Indeed, in this particular case, it doesn't. It does in the cases...

Tab completion is already mentioned in https://github.com/pyenv/pyenv?tab=readme-ov-file#set-up-your-shell-environment-for-pyenv . Perhaps we can make the mention more prominent (e.g. explicitly call it "tab completion")? Tab completion -- and the ability for programs...

> Would you consider at least in case is user want to delete python version, e.g. 3.7.14, but writes only `pyenv uninstall 3.7` pyenv telling him "Hey the version 3.7...

[We already do checksum verification](https://github.com/pyenv/pyenv/tree/master/plugins/python-build#checksum-verification). Unless I'm misunderstanding you.

> verification of those checksums against the expected release manager identity So we'll have to somehow track this "release manager identity"? Because I surmise it's going to change with some...

Since this is a limitation of `setup.py`, this is an issue of whatever Python you're compiling, not of Pyenv. Pyenv diligently passes `MAKE_OPTS`/`MAKEOPTS` to the `make` invocation _it_ makes and...

@JustAnotherArchivist You _can_ add a patch for the Python version(s) you're experiencing problems with. See the patches in Python-build on how it's done.

As specified earlier, we'll accept a patch from any interested parties. There are only a few ways to pass `-j`, it's not prohibitive to recognize them all, e.g. with a...

https://github.com/pyenv/pyenv/wiki/Common-build-problems#build-failed---bad-interpreter-permission-denied

> the same with Python 3.11.4 > > Would it make sense to re-open this issue because automatic installation does not work on MacOS arm64 ? Pyenv can't fix the...