It has been recalled due to introducing an unexpected incompatibility:
https://www.python.org/downloads/release/python-393/

The original 2.3 portable version was compiled on Ubuntu 20.04 and didn't work with older glibc.

This has been fixed and the older file has been deleted so hopefully this change is acceptable.

fix: correct the reported version for 3.10.0b4

Add Pyston 2.3

3.10.0b4

* In some cases (Ubuntu), `pyenv init -` has to be run before `pyenv init --path`.
* The warning has served its purpose by now.

Miniforge minor update to 4.10.1-5

Suggest that fish users init in interactive mode

...rather than login mode.

I couldn't get rid of the warning that `pyenv init -` no longer sets path until I did this. It looks like setting only on the login shell wasn't enough to hide the warning in other shells I opened. This fits with [how rbenv does the same thing](https://github.com/rbenv/rbenv/blob/master/libexec/rbenv-init#L74).

I'm way out of my depth here, so someone who knows about shell types should definitely review this.

* Add 3.10.0b3

Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

Revert "Drop inferring version to install from `pyenv local`"

PEP 394 now doesn't require `python` presence or specify what it is.
Tests that invoke it use Py3-specific code.

Closes https://github.com/pyenv/pyenv/issues/1921

Debian/Ubuntu's stock `~/.bashrc` prepends `~/.local/bin` to `PATH` towards its end if it exists.
Executables for per-user modules for system Python are installed into `~/.local/bin` --
so need to prepend `shims` to `PATH` later that that.

Co-authored-by: Ivan Pozdeev <vano@mail.mipt.ru>

Drop inferring version to install from `pyenv local`

Create mambaforge-4.10.1-4

Change `done` to `fi` since otherwise Bash emits an unexpected token error:

```
bash: /home/foo/.bashrc: line 120: syntax error near unexpected token `done'
bash: /home/foo/.bashrc: line 120: `if command -v pyenv >/dev/null; then eval "$(pyenv init -)"; done'
```

Add explicit Zsh instructions for MacOS

Indirect ones with errata have proven to confuse users.
Fixes #1947, #1948

install pip with pyston

The default pyston build do not have pip installed by default. This change just add `get_pip` function to have pip installed.

Mention log file if an error happened before building, too

Add pypy3.7-7.3.5, pypy3.7-7.3.4-src, pypy3.7-7.3.5-src

Report cache filename at download