Should initialization errors be exposed to the user?

Assessment

Research direction

Description

Currently, if user configures InteractiveShellApp.exec_lines and it fails, there is no way for them to see the error in notebook.

For example set c.InteractiveShellApp.exec_lines=["raise ValueError()"].

This is visible in IPython/jupyter-server because it gets written to the terminal, but it does not show up in the notebook. There is even explicit code making sure that it won't be attached to the output of the first cell once it gets run:

https://github.com/ipython/ipykernel/blob/84211d7227fd5faa9d6e485641c1a4df6e7df2b4/ipykernel/kernelapp.py#L730-L737

With code to the same effect in IPython itself: https://github.com/ipython/ipython/blob/cc614bdc1d3f61303e265c26d593d384e4a90d1e/IPython/core/shellapp.py#L341-L360

I wonder if we should emit a special message for any output so that it would be shown in the Notebook console? The same way as unhandled ipywidget messages land in the console?

I mean this log console:

Contributor guide

Open the contributing guide

First steps

1. Read the whole issue, then the project's contributing guide.
2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
3. Fork the repository and make your change on a branch.
4. Open a pull request that references the issue number.

More from ipython/ipykernel

• `Kernel._control_lock` created after it may be used Open

  Difficulty 2/5 1-3 hours Newbie friendliness 75/100

  ipython/ipykernel#1567 · 1 comment · Opened Sep 22, 2026

• pytest seems to be the testrunner - not nose, as mentioned in README Open

  Difficulty 1/5 Under an hour Newbie friendliness 72/100

  ipython/ipykernel#554 · Opened Oct 17, 2020

• post_execute fires during comm_msg handling on a subshell, so output published from the hook is parented to the comm_msg and dropped by frontends Open

  Difficulty 4/5 3-5 days Newbie friendliness 48/100

  ipython/ipykernel#1564 · Opened Sep 21, 2026

• Shell reply sent raw on the ROUTER can drop the ZMQStream wake-up; a request arriving in that window is not read until the next connection Open

  Difficulty 4/5 3-5 days Newbie friendliness 68/100

  ipython/ipykernel#1554 · 1 comment · Opened Sep 7, 2026

• Interrupt on swallowed `KeyboardInterrupt` exceptions (`SIGINT`) when pressing twice (within 5 seconds) Open

  ipython/ipykernel#1550 · 1 comment · 1 reaction · 1 assignee · Opened Aug 25, 2026

All issues in ipython/ipykernel

Similar issues

• [essnmx] Fix typo in NXLauetof application definition Open
  essnmx good first issue

  Difficulty 1/5 Under an hour Newbie friendliness 95/100

  scipp/ess#760 · Opened Sep 23, 2026

• [Feature] 奇物选择添加优先级 Open

  Difficulty 2/5 1-3 hours Newbie friendliness 65/100

  syfoud/Simulated_Scepter#174 · Opened Sep 23, 2026

• garak adapter grades a NaN detector score as PASS Open

  Difficulty 2/5 1-3 hours Newbie friendliness 75/100

  Giskard-AI/giskard-oss#2840 · 1 comment · Opened Sep 23, 2026

• A claim comment carrying the issue number is silently declined while the workflow reports success Open
  area: repo bug perceived difficulty: 2

  Difficulty 2/5 1-3 hours Newbie friendliness 70/100

  Nitjsefnie-Harness-Commons/daedalus#926 · Opened Sep 23, 2026

• `IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

  Difficulty 2/5 1-3 hours Newbie friendliness 75/100

  yeti-platform/yeti#1380 · Opened Sep 23, 2026

More Python issues