nteract/papermill

Add the output notebook object to PapermillExecutionError

Open

#795 建立於 2024年5月3日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Python (5,381 star) (402 fork)batch import
enhancementhelp wanted

描述

🚀 Feature

Add the output notebook object to PapermillExecutionError

Motivation

When running the notebook using python, the only current way to access the output notebook on an exception is by writing the notebook to an I/O handler. If all we need to do in the application executing the notebook is to inspect the notebook (for instance for looking for data attached with a library like scrapbook), we have to write the notebook to the I/O handler, then reconstitute it after handling the exception. This is slow(er), and a bit of a challenge when all we want is the notebook object AFTER an exception.

貢獻者指南

技術棧
python
領域
databackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonPapermillJupyter notebooks
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
The PapermillExecutionError class is likely defined in the papermill package. Examine the exception handling where execute notebook raises errors. The goal is to store the output notebook object (a nbformat.NotebookNode) as an attribute of the exception. Look for the execute notebook function and related classes to understand where the notebook object is available and how to attach it to the exception before raising.