Update to version 1.0.0a9

[shiroinekotfs]

This update has significant changes, including bug fixes and new features, to improve user experience, performance, and security.

Improvements

• As discussed in Change C++ std to whatever gcc supports #28, the new C++ kernel will include all possible C++ standards, each supporting its configured standard (C++98, C++03, C++11, C++14, C++17, C++20, C++23). To achieve this, @anhvlt-2k6 had to move the kernel core into a separate package and rewrite it to accept the connection from the Jupyter to the kernel core.

Note that the default standard for documentation is C++14.

• The execution time is down from ~2.4s in 1.0.0a8 to ~750ms (3x faster). It can be done by removing the regex resolution, replace it with the C++ implementation; as well as some functions in _Jupyter_Display (for MimeHandler there are _jupyter_font, _jupyter_example, _jupyter_message, _jupyter_model, and _jupyter_multipart; YouTubePlayer, OBJ, and CSV). Other MIME types will be added in the next release of the kernel (1.0.0a10).

• Adding new standard for including default headers (classic C standards come first, then the C++ headers, then customized headers). It is, to make sure that every functional aspect of the customized header will replace the default parameter, and by that, will extend the functionality of the kernel.

• New kernel requires a new version of Python 3.9. Python 3.8 is no longer supported, since it contains security issues, which may lead to code injection, causing a dangerous effect on the kernel, and the server as well.

• New logic, math constants, and trigonometry measurements.

• Kernel doesn't work with VS code #37 will be fixed.

New standards for C++ kernel have been added

Credits

Thanks to @anhvlt-2k6 for supporting the project.

Also, thanks to @fadyosman and @ShashaankHari for great contribution to the project.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[anhvlt-2k6]

To be honest, I don't know how to let the kernel run on Visual Studio Code. The VS Code and Jupyter Lab/Notebook seem running different APIs.

[ShashaankHari]

To be honest, I don't know how to let the kernel run on Visual Studio Code. The VS Code and Jupyter Lab/Notebook seem running different APIs.

Actually don't mind it, I was running your kernel inside vs code only way back, not much of a hassle. Inside jupyter's config(vscode) you can add custom kernel paths and then choose the kernel in the selection when you create a new notebook.

[shiroinekotfs]

To be honest, I don't know how to let the kernel run on Visual Studio Code. The VS Code and Jupyter Lab/Notebook seem running different APIs.

As I debug the kernel, there is a problem with the kernel. Debug Information:

• OS: Windows 11 24H2 x64
• Environment: Conda Python 3.13.2
• Debug Logging:

3:05:53.236 [info] Starting Kernel (Python Path: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe, Conda, 3.13.2) for 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb' (disableUI=false)
23:05:53.413 [info] Launching Raw Kernel C++ 03 # python3
23:05:53.418 [info] Process Execution: python3 -m jupyter-cpp-kernel-03 -f c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json
    > cwd: f:\~tfs\jupyter-cpp-kernel-doc\I. The basics
23:05:53.419 [error] Kernel died Error: spawn python3 ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn python3',
  path: 'python3',
  spawnargs: [
    '-m',
    'jupyter-cpp-kernel-03',
    '-f',
    'c:\\Users\\~\\AppData\\Roaming\\jupyter\\runtime\\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json'
  ]
} 
23:05:53.419 [error] Disposing kernel process due to an error Error: spawn python3 ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn python3',
  path: 'python3',
  spawnargs: [
    '-m',
    'jupyter-cpp-kernel-03',
    '-f',
    'c:\\Users\\~\\AppData\\Roaming\\jupyter\\runtime\\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json'
  ],
  vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
23:05:53.419 [error] 
23:05:53.420 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
23:05:53.420 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
23:05:53.421 [warn] Failed to shutdown kernel, .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file} TypeError: Cannot read properties of undefined (reading 'dispose')
    at Z_.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:301:13745)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at eT.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:301:22578)
23:05:53.421 [warn] Error occurred while trying to start the kernel, options.disableUI=false Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.421 [warn] Kernel Error, context = start Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.427 [info] Process Execution: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
23:05:53.846 [info] Dispose Kernel 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb' associated with 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb'
23:05:53.847 [error] Error in notebook cell execution Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.847 [error] Error in execution (get message for cell) Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.852 [info] Process Execution: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"

---

Edit: It seems running the Jupyter Notebook server, and then letting the Visual Studio Code connect to the server (via token, password, etc.) is the only way to let the C++ kernel run. Here is the prove (I connect my VS Code Notebook to the Jupyter Notebook server at localhost:8888)

[anhvlt-2k6]

To be honest, I don't know how to let the kernel run on Visual Studio Code. The VS Code and Jupyter Lab/Notebook seem running different APIs.

As I debug the kernel, there is a problem with the kernel. Debug Information:

• OS: Windows 11 24H2 x64
• Environment: Conda Python 3.13.2
• Debug Logging:

3:05:53.236 [info] Starting Kernel (Python Path: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe, Conda, 3.13.2) for 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb' (disableUI=false)
23:05:53.413 [info] Launching Raw Kernel C++ 03 # python3
23:05:53.418 [info] Process Execution: python3 -m jupyter-cpp-kernel-03 -f c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json
    > cwd: f:\~tfs\jupyter-cpp-kernel-doc\I. The basics
23:05:53.419 [error] Kernel died Error: spawn python3 ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn python3',
  path: 'python3',
  spawnargs: [
    '-m',
    'jupyter-cpp-kernel-03',
    '-f',
    'c:\\Users\\~\\AppData\\Roaming\\jupyter\\runtime\\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json'
  ]
} 
23:05:53.419 [error] Disposing kernel process due to an error Error: spawn python3 ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn python3',
  path: 'python3',
  spawnargs: [
    '-m',
    'jupyter-cpp-kernel-03',
    '-f',
    'c:\\Users\\~\\AppData\\Roaming\\jupyter\\runtime\\kernel-v32f19567974b244d9b36b85fe36d85f6cb00647ad.json'
  ],
  vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
23:05:53.419 [error] 
23:05:53.420 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
23:05:53.420 [error] Failed to connect raw kernel session: Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
23:05:53.421 [warn] Failed to shutdown kernel, .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file} TypeError: Cannot read properties of undefined (reading 'dispose')
    at Z_.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:301:13745)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at eT.shutdown (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:301:22578)
23:05:53.421 [warn] Error occurred while trying to start the kernel, options.disableUI=false Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.421 [warn] Kernel Error, context = start Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.427 [info] Process Execution: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
23:05:53.846 [info] Dispose Kernel 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb' associated with 'f:\~tfs\jupyter-cpp-kernel-doc\I. The basics\2. Variables and types.ipynb'
23:05:53.847 [error] Error in notebook cell execution Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.847 [error] Error in execution (get message for cell) Error: The kernel died. Error: ... View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd061beec637bd29806ccbde465cd03d9fc7f63a20e4ef387fff58306a0828bd736#cpp03.c:\Users\~\anaconda3\envs\jupyter-cpp-kernel\python.exe.\.python3#-m#jupyter-cpp-kernel-03#-f#{connection_file}
    > Interpreter Id = c:\USERS\~\ANACONDA3\ENVS\JUPYTER-CPP-KERNEL\PYTHON.EXE
    > at new n (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2025.2.0-win32-x64\dist\extension.node.js:98:4480)
    > originalException = Error: spawn python3 ENOENT
    > stdErr = 
23:05:53.852 [info] Process Execution: ~\anaconda3\envs\jupyter-cpp-kernel\python.exe -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"

Edit: It seems running the Jupyter Notebook server, and then letting the Visual Studio Code connect to the server (via token, password, etc.) is the only way to let the C++ kernel run. Here is the prove (I connect my VS Code Notebook to the Jupyter Notebook server at localhost:8888)

Thanks for your recent update. I think the problem may start with both kernel and the VS Code itself, since the C++ kernel use the ipykernel start-up procedures, and the VS Code uses IPython (I guess so, according to your logs)