firai

Not sure if this helps with finding the issue, but this is the debug log I get when I try to run qtconsole with PyPy v7.3.9 and Pyside6 v6.3.0 on...

Just to be clear, qtconsole works with the WinPython setup under CPython 3.10.0 and Pyside6 6.3.0 (i.e. same version of Pyside6 as the PyPy setup), so it seems like the...

Well something strange is happening: qtconsole fires up if I run it through gdb or WinDbg. Note that the ipykernel dies at least once before working properly in both cases....

I'm also adding WinDbg analysis of the crash dump that gets generated when I run qtconsole without executing through gdb or WinDbg, in case this helps. However, since this is...

Just for documentation purposes, qtconsole run without gdb or WinDbg on PyPy sometimes dies with the faulting module as ntdll, as called from QtCore, instead of Shiboken6 as described above....

Also for documentation purposes, I finally got a chance to try this on Linux (well technically WSL) PyPy. Also seems like some sort of race condition here, as I'm getting...

Not a Mac user, but try installing Homebrew through a Rosetta terminal, and then install x86-64 Python through that?

Also, you should use Python 3.9. Opspy seems to have dependency issues on 3.10 (i.e. the maintainers have locked the requires to 3.9).

I'm not sure if this belongs here or in a separate issue, but is there a reason why JupyterLab isn't started in the Gitpod setup with the `--collaborative` flag by...

@jtpio I created a PR at https://github.com/jupyterlab/jupyterlab/pull/13239 to add the `--collaborative` flag. > They are pretty generous with the specs of the machines (for now at least), so that could...