{"library":"jupyter-console","title":"Jupyter Console","description":"Jupyter Console is a terminal-based console frontend for Jupyter kernels, offering an interactive computing experience directly in your terminal. It provides a rich interface for interacting with various Jupyter kernels, including Python, Julia, and R, building upon the single-process IPython terminal. The current version is 6.6.3 and it is actively maintained as part of the broader Project Jupyter ecosystem, with releases typically tied to updates in its subprojects.","status":"active","version":"6.6.3","language":"en","source_language":"en","source_url":"https://github.com/jupyter/jupyter_console","tags":["jupyter","console","terminal","interactive","cli","kernel"],"install":[{"cmd":"pip install jupyter-console","lang":"bash","label":"Install with pip"}],"dependencies":[],"imports":[{"note":"Most users interact with jupyter-console via the command-line; direct programmatic import for launching the console is less common.","symbol":"JupyterConsoleApp","correct":"from jupyter_console.app import JupyterConsoleApp"}],"quickstart":{"code":"jupyter console --kernel=python","lang":"bash","description":"Launch an interactive Python console session in your terminal. If no kernel is specified, it will attempt to find a default Python kernel."},"warnings":[{"fix":"Review custom code that relies on IPython's internal shell architecture and adapt to jupyter-console's separated `ZMQTerminalInteractiveShell`.","message":"Version 5.0 introduced significant architectural changes, notably disinheriting the shell class from IPython's interactive shell. This may affect advanced users who were directly subclassing or heavily customizing IPython's internal shell structures for jupyter-console.","severity":"breaking","affected_versions":">=5.0.0"},{"fix":"Ensure packages are installed in the Python environment associated with the kernel being used by `jupyter-console`. Use `import sys; print(sys.prefix)` inside the console to verify the active environment.","message":"When multiple Python environments are present, `ImportError: No module named...` errors can occur if the Jupyter kernel runs in a different environment than where a package was installed.","severity":"gotcha","affected_versions":"All versions"},{"fix":"Update configuration files or programmatic settings to use `JupyterConsoleApp.confirm_exit` instead of the old path.","message":"The configuration option for confirming exit (`confirm_exit`) was moved from `ZMQTerminalInteractiveShell.confirm_exit` to `JupyterConsoleApp.confirm_exit` in version 5.3.","severity":"gotcha","affected_versions":">=5.3.0"},{"fix":"To gracefully quit both the console and stop the kernel in such scenarios, use `Ctrl-\\` (Ctrl-Backslash) instead of `Ctrl-D`.","message":"Exiting `jupyter console` with `Ctrl-D` when it's connected to a kernel *not* started by the console itself will leave the kernel running.","severity":"gotcha","affected_versions":"All versions"}],"env_vars":null,"last_verified":"2026-04-05T00:00:00.000Z","next_check":"2026-07-04T00:00:00.000Z"}