native-api

We need a full debug trace of a faulty Pyenv invocation as explained in the issue template to diagnose a problem. 1.2.20 is also quite old, check if it works...

I'm not quite sure "what you're asking for". Let's find that out. From what I can see, Jupyter is started with `jupyter lab`. Since `jupyter` is Python-based, it belongs to...

Since that process presumably doesn't use the shell or even call any external programs in the discovery process, there's nothing Pyenv can do to intercept it. We can however e.g....

So there are 2 options: 1. Install Jupyter for all the Python versions you'll be using it with -- then just select the version with Pyenv, run `jupyter` and use...

Okay, with this explanation, I now see what you're talking about. The reason is that Pyenv sets the `PYENV_VERSION` envvar in the environment of the executed command. Looking at the...

> The script sage-bootstrap-python attempts to call a command like "/path/to/python" -c "..." Pyenv python treats "python" differently from just python, giving the output: /home/.../.pyenv/shims/python: line 1: 2: command not...

Then we need diagnostic information as per the issue template to be able to say anything more specific.

> The trace.log file only contains `/home/k3w1k0d3r/.pyenv/shims/python: line 1: 2: command not found` That qualifies and is helpful. There's no '2' on line 1 of a correct shim. Something must...

Also check if you have any shell aliases set.

Interesting. That alias must be the reason. It must be getting substituted somewhere during shim creation. Please provide a tracelog of `pyenv rehash`.