Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://jupyterlab.readthedocs.io/en/stable/getting_started/../user/documents_kernels.html below:

Documents and Kernels — JupyterLab 4.4.4 documentation

In the Jupyter architecture, kernels are separate processes started by the server that run your code in different programming languages and environments. JupyterLab enables you to connect any open text file to a code console and kernel. This means you can easily run code from the text file in the kernel interactively.

Right-click on a document and select “Create Console for Editor”:

Once the code console is open, send a single line of code or select a block of code and send it to the code console by hitting Shift Enter:

In a Markdown document, Shift Enter will automatically detect if the cursor is within a code block, and run the entire block if there is no selection:

Any text file (Markdown, Python, R, LaTeX, C++, etc.) in a text file editor can be connected to a code console and kernel in this manner.

For kernels that support subshells (such as Python kernels with ipykernel 7.0.0+), you can create a subshell console to run code concurrently with the main notebook execution.

Creating a Subshell Console:

1. Command Palette: Press Ctrl+Shift+C (Cmd+Shift+C on Mac) and search for “New Subshell Console for Notebook”

2. Context Menu: Right-click in a notebook and select “New Subshell Console for Notebook” (only appears if kernel supports subshells)

Verifying Subshell Functionality:

Use the %subshell magic command in Python kernels:

This displays:

• subshell id: None for main shell, or a unique ID for subshells

• subshell list: Array of active subshell IDs

Practical Example:

1. In your main notebook, start a long-running computation:

   import time
   for i in range(100):
       print(f"Main shell: {i}")
       time.sleep(1)
   

2. While this runs, create a subshell console and execute:

   print("This runs concurrently!")
   %subshell  # Shows this subshell's ID
   

3. The subshell executes immediately without waiting for the main shell to finish.

Communication Settings

Configure how widget communications use subshells via Settings → Advanced Settings → Kernel:

• disabled: No subshells for communications

• perCommTarget: One subshell per communication target (default)

• perComm: One subshell per communication (can create many subshells)

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4