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

* Added Stackless 2.7.16

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

Prevent build from installing MacOS apps globally

ldflags_dirs is not needed for Python and causes failures

Update anaconda3-2021.05 - fixed checksum for macOS package

Fixed checksum for macos package

Ensuring that all dirs in LDFLAGS exist is only needed for Ruby due to its `configure` requirements.
If some LDFLAGS entries point to a nonexisting path to which the user doesn't have permission. this causes a build failure.

The $(type -p | head -1) construct expects to always get a path, so need to ignore such aliases with -P

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

E.g. "*-latest"
May need splitting into project-specific ones if there emerge projects with different check needed

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

Create miniforge3-4.10.1-1

Make test independent of umask

Bash automated install option for the case when ~/.profile sources ~/.bashrc

* Update install instructions for Bash and Zsh

* Synchronize README.md with `pyenv init`
* Add a ~/.bash_profile note
* Concatenate shims activation into installation for brevity
  (Pyenv can't be used meaningfully without shims anyway)
  Otherwise, we'd need to duplicate all the ~/.profile shenanigans in both sections
* Update based on feedback
* Proofread

Add a hint for cases when ~/.profile sources ~/.rc

Our ~/.rc logic must run after the ~/.profile one

Place full shell configuration instructions into `pyenv init`

including initial PATH and PYENV_ROOT entries.
The migration hint proved to be unclear to users without them.

In certain cases, a user wants to know the cached filename to add the file themselves,
see https://github.com/pyenv/pyenv/issues/1743 .
Since we report both a filename and a URL anyway, there's no reason to report a wrong one.

Update generated configuration files before run ./configure

This behavior is only triggered when the version is provided as an empty string,
is undocumented and breaks if multiple local versions are specified
(rightly so since it's unclear which of them to install).

Only test the permission bit that we're setting

Split startup logic into PATH and everything else

E.g. for a GUI session, ~/.profile is executed by the GUI login "shell" at its startup
so one needs to fully log out and log back in.
Before that, the change would only be seen by shells explicitly started as login shells.