put your comments on the subject in the discussion here rather than in#966

The idea is very simple:

• to improve 'official' Python cPython speed, you need more competition urgently
• if the competition is internal, you improve your two horses per benchmarking one to the other
• hope is also to improve the inter-connexion (HPy) and reduce version lag of PyPy along the way.

Dreamed Roadmap:

• WinPython 2021-03: PyPy-7.3.5 for Python3.7+ VSCode + Jupyterlab + Cython, on 64 bit only
• WinPython 2021-04: HPy and performances fixes
• WinPython 2021-05: PyPy for Python-3.8
• WinPython 2022-01: PyPy for Python-3.9
• WinPython 2022-03: PyPy for Python-3.10
• WinPython 2022-05: PyPy for Python-3.11

The nextPython Langage Summit, may 10th 2021, will show the different speed-up initiatives ongoing:

• Core cPython developers:
  • PEP 654 - Exception Groups and except* (asyncio simplified)
  • Progress on running multiple Python interpreters in parallel in the same process
• Core PyPy developers:
  • HPy: Present & Future (may get support also from GraalPython and RustPython team)
• Instagam/Facebook:
  • CPython improvements at Instagram (by former Microsoft/Pyjion developer)

At same time, Microsoft:

• did a new release of Pyjion
• did a new release of IronPython