Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jupyter-available-kernelspecs fails with Python 3.11 #436

Closed
dlukes opened this issue Feb 16, 2023 · 0 comments
Closed

jupyter-available-kernelspecs fails with Python 3.11 #436

dlukes opened this issue Feb 16, 2023 · 0 comments

Comments

@dlukes
Copy link

dlukes commented Feb 16, 2023

jupyter kernelspec list --json emits a warning to stderr, which jupyter-available-kernelspecs fails to separate from stdout, and therefore parsing fails:

0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
{
  "kernelspecs": { ... }
}

The warning is emitted by pydevd, vendored by debugpy, required by ipykernel.

Workaround: setting the environment variable PYDEVD_DISABLE_FILE_VALIDATION=1 to silence the warning (as suggested by the message). Ignoring the warning should be safe with recent enough versions of debugpy since microsoft/debugpy#937.

Fix: jupyter-command should discard stderr, or possibly output it as a message, instead of combining it with stdout.

eginhard pushed a commit to eginhard/emacs-jupyter that referenced this issue Dec 10, 2023
Write stderr content as a message to the user.  Closes emacs-jupyter#436.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant