Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Cling Jupyter kernel not working

Abierto
  • ¿Algo no está bien?
#511 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
cpp, jupyter, python
Área
tooling

Línea de trabajo

The steps start in tools/Jupyter/kernel in the cling source tree, where pip install -e . and jupyter-kernelspec install register the four C++ kernels. The reported error is spawn Jupyter-Cling-Kernel ENOENT, so begin by checking the kernel.json launch entries and whether the Jupyter-Cling-Kernel executable exists on Windows PATH. Done means a registered kernel starts and runs a cell on Windows. The thread has no reply in about three years and no fix, so expect to reproduce the environment first.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

After Cling entire build, the Cling executable works very well. But I've found that Jupyter Tools is not found in<CLING_INSTALL_PATH>/share/location.

Then I navigate to source location<CLING_SRC_PATH>/tools/cling/tools/Jupyter/kerneland do the register Jupyter kernel by Install clingKernel and jupyter-kernelspec:

  • PowerShell/CMD Shell
  pip install -e .

  jupyter-kernelspec install cling-cpp17
  jupyter-kernelspec install cling-cpp1z
  jupyter-kernelspec install cling-cpp14
  jupyter-kernelspec install cling-cpp11

Here comes with two Cling Jupyter kernel not working status:

By using VSCode Jupyter Notebook

First I want try in vscode and been denied execute to run kernel by told that cling Jupyter kernels must add to trusted kernels in settings.json, then I added 4 kernels in settings and showed running error with message "spawn Jupyter-Cling-Kernel ENOENT" error.

By using Webpage Jupyter Notebook

Assume if it's only vscode extentions' compatability caused problems, I tried using individual terminal running local Jupyter server, exclude "403 Forbidden" error status, whatever using Edge or Chrome can logging create a notebook actaully can select 4 kernels "C++17", "C++1z", "C++14" and "C++11" with kernel connection status "Unknown Kernel" and won't work.

In conclution I think is the kernel settings error, not VSCode's problem. I ensured Cling and Python's Install path has been added to PATH, both can be called in terminal. Is there anyway can modify the kernel register settings or need to rebuild/reinstall?

Lenguaje dominante
C++
Estrellas
4.2k
Forks
313
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de root-project/cling

Todos los issues de root-project/cling

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.