Spyder , qtconsole, pyzo are not yet working with pypy.
Minimal progress on this in 3 months.
Let hope it improves with pypy-3.9

Ok, thanks. If so, my guess is that this should be much clearer on the main https://winpython.github.io/ page

It will likely be a while before Spyder works on PyPy. At the moment, Spyder isn't compatible with Qt 6 in general, while Qt 6 is the only version of Qt that has been made (somewhat) compatible with PyPy via PySide6 6.3.

Furthermore, due to the nature of PyPy's JIT and the generated C-code, it's incredibly difficult to trace and produce minimal reproducible examples of Qt bugs on PyPy. For example, we still haven't been able to produce one for spyder-ide/qtconsole#535 yet. Per the PySide repo, there are a number of tests failing that are likely to difficult to debug, and the Qt team is probably not going to be motivated to spend a lot more time working on this until the community shows more interest. And as far as I can tell, there aren't any community-reported PyPy-related bugs filed in the PySide repo yet. The best way to get this moving is to work toward minimal reproducible examples of the incompatibilities and file them in the respective repos.

PySide6 Development notes of July 14th suggests that they are working on CI integration of PyPy.
It's moving more slowly than hoped, may wake-up a bit when PyPy-3.9 will be declared stable.

Correction to my previous comment: there now seems to be one community-reported PyPy-related bug filed in the PySide repo, filed by a PyQtGraph core dev. See https://bugreports.qt.io/browse/PYSIDE-1991. Not sure if this segfault is the same or related to the one that we are observing with qtconsole.

Spyder will move to PyQt6, maybe end 2023. Not before that time shall we expect it to have a chance to work well with PyPy/Pyside6

as cPython is progressing on JIT and nogil, and pypy was a big deception in jupyterlab responsiveness.

pypy project is quite a "visionnary" 15 years ahead project:

• with THE expertise in nogil , jit, utf-8 , hpy
• pieces are percolating with cpython, around python-3.15 by the smell of it (instead of hoped 3.14)
• but supporting it was too much effort for tool little benefit, as the speed benefit was negative on responsiveness, on Windows at least