nteract/papermill

Add the output notebook object to PapermillExecutionError

Open

Aperta il 3 mag 2024

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)Python (5381 star) (402 fork)batch import
enhancementhelp wanted

Descrizione

🚀 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.

Guida contributor

Tech stack
python
Dominio
databackend
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
PythonPapermillJupyter notebooks
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
70
Direzione di ricerca
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.