PyPy 7.3 Beta Build 3 - Qtconsole Issue #1068

firai · 2022-04-24T15:43:32Z

firai
Apr 24, 2022

@stonebig With regards to spyder-ide/qtconsole#535, it seems like the problem could be partly originating from an incompatibility in the current build with Jupyter or some component thereof. It doesn't seem appropriate to flood that issue with further discussion about resolving build issues, so I'll post here instead.

In an effort to isolate the problem, I tried get access to the command line Jupyter console with .\pypy.exe -m jupyter console, and the console successfully starts:

Jupyter console 6.4.0

Python 3.8.12 (0089b4a7ab2306925a251b35912885d52ead1aba, Mar 16 2022, 13:51:04)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.32.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]:

However, when I try to do anything, such as press enter or run a simple command (print(1)), I get an exception. I think I have isolated the issue to Jupyter rather than IPython, because I connected a CPython Jupyter console to a PyPy IPython kernel, and that worked OK.

Unhandled exception in event loop:
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\Lib\asyncio\events.py", line 81, in _run
    self._context.run(self._callback, *self._args)
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\Lib\_contextvars.py", line 43, in run
    return callable(*args, **kwargs)
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\input\win32.py", line 612, in ready
    callback()
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\application\application.py", line 710, in read_from_input
    self.key_processor.process_keys()
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\key_binding\key_processor.py", line 270, in process_keys
    self._process_coroutine.send(key_press)
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\key_binding\key_processor.py", line 185, in _process
    self._call_handler(matches[-1], key_sequence=buffer[:])
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\key_binding\key_processor.py", line 320, in _call_handler
    handler.call(event)
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\prompt_toolkit\key_binding\key_bindings.py", line 124, in call
    result = self.handler(event)
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\jupyter_console\ptshell.py", line 475, in _
    self.handle_iopub()
  File "C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\jupyter_console\ptshell.py", line 854, in handle_iopub
    msg_type = sub_msg['header']['msg_type']

Exception 'coroutine' object is not subscriptable (key 'header')

I haven't had time to dig deeper, but this problem seems to suggest that something's wonky between PyPy and Jupyter in the current build.

I didn't get anything meaningful from qtconsole's debug output before it auto-quits, so I started suspecting that the problem might not be with Pyside6.

[JupyterQtConsoleApp] Searching ['C:\\Users\\xxx\\Desktop\\WPy64-38122b3\\pypy3.8-v7.3.9-win64', 'C:\\Users\\xxx\\.jupyter', 'C:\\Users\\xxx\\AppData\\Roaming\\PyPy\\etc\\jupyter', 'C:\\Users\\xxx\\Desktop\\WPy64-38122b3\\pypy3.8-v7.3.9-win64\\etc\\jupyter', 'C:\\ProgramData\\jupyter'] for config files
[JupyterQtConsoleApp] Looking for jupyter_config in C:\ProgramData\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\AppData\Roaming\PyPy\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\.jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\ProgramData\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\AppData\Roaming\PyPy\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\.jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64
[JupyterQtConsoleApp] Connecting to existing kernel: C:\Users\xxx\AppData\Roaming\jupyter\runtime\kernel-11904.json
[JupyterQtConsoleApp] Loading connection file C:\Users\xxx\AppData\Roaming\jupyter\runtime\kernel-11904.json

firai · 2022-04-24T17:07:53Z

firai
Apr 24, 2022
Author

Update: upgrading to jupyter-console 6.4.3 seems to have (mostly) fixed the issue above (see jupyter/jupyter_console#241 (comment)). However, qtconsole is still not starting. The current debug message is:

[JupyterQtConsoleApp] Searching ['C:\\Users\\xxx\\Desktop\\WPy64-38122b3\\pypy3.8-v7.3.9-win64', 'C:\\Users\\xxx\\.jupyter', 'C:\\Users\\xxx\\AppData\\Roaming\\PyPy\\etc\\jupyter', 'C:\\Users\\xxx\\Desktop\\WPy64-38122b3\\pypy3.8-v7.3.9-win64\\etc\\jupyter', 'C:\\ProgramData\\jupyter'] for config files
[JupyterQtConsoleApp] Looking for jupyter_config in C:\ProgramData\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\AppData\Roaming\PyPy\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\.jupyter
[JupyterQtConsoleApp] Looking for jupyter_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\ProgramData\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\AppData\Roaming\PyPy\etc\jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\.jupyter
[JupyterQtConsoleApp] Looking for jupyter_qtconsole_config in C:\Users\xxx\Desktop\WPy64-38122b3\pypy3.8-v7.3.9-win64
[JupyterQtConsoleApp] Connecting to existing kernel: C:\Users\xxx\AppData\Roaming\jupyter\runtime\kernel-11904.json
[JupyterQtConsoleApp] Loading connection file C:\Users\xxx\AppData\Roaming\jupyter\runtime\kernel-11904.json
[JupyterQtConsoleApp] connecting shell channel to tcp://127.0.0.1:49527
[JupyterQtConsoleApp] Connecting to: tcp://127.0.0.1:49527

2 replies

stonebig Apr 24, 2022
Maintainer

I get this message while trying jupyter-console-6.4.3, that you don't seem to have? not sure if there is a correlation

C:...\WPy64-38122b3\pypy3.8-v7.3.9-win64\lib\site-packages\zmq\_future.py:591: RuntimeWarning: Proactor event loop does not implement add_reader family of methods required for zmq. Registering an additional selector thread for add_reader support via tornado. Use `asyncio.set_event_loop_policy(WindowsSelectorEventLoopPolicy())` to avoid this warning.
  self._get_loop()
Jupyter console 6.4.3

Python 3.8.12 (0089b4a7ab2306925a251b35912885d52ead1aba, Mar 16 2022, 13:51:04)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.32.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: for i in range(3): print(i)
0
1
2

In [2]:
``

firai Apr 25, 2022
Author

I do get the error, but it doesn't stop qtconsole from working on CPython builds (which also exhibits the same error). I believe the error is related to breaking changes in how Python >= 3.8 works. See tornadoweb/tornado#2608, which you seem to have participated in.

stonebig · 2022-04-24T17:23:02Z

stonebig
Apr 24, 2022
Maintainer

I'm surprised I didn't get latest Jupyter-console... checking why.
also, WinPython ways can create troubles and bugs of their own.

hum....

Installing collected packages: jupyter-client, jupyter-console
  Attempting uninstall: jupyter-client
    Found existing installation: jupyter-client 6.2.0
    Uninstalling jupyter-client-6.2.0:
      Successfully uninstalled jupyter-client-6.2.0
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
voila 0.2.16 requires jupyter-client<7,>=6.1.3, but you have jupyter-client 7.2.2 which is incompatible.
Successfully installed jupyter-client-7.2.2 jupyter-console-6.4.3

will remove voila from PyPy builds for now.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

PyPy 7.3 Beta Build 3 - Qtconsole Issue #1068

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 2 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

PyPy 7.3 Beta Build 3 - Qtconsole Issue #1068

firai Apr 24, 2022

Replies: 2 comments · 2 replies

firai Apr 24, 2022 Author

stonebig Apr 24, 2022 Maintainer

firai Apr 25, 2022 Author

stonebig Apr 24, 2022 Maintainer

firai
Apr 24, 2022

Replies: 2 comments 2 replies

firai
Apr 24, 2022
Author

stonebig Apr 24, 2022
Maintainer

firai Apr 25, 2022
Author

stonebig
Apr 24, 2022
Maintainer