nteract/papermill

Option to keep notebook open after run for debugging

Open

#641 opened on Nov 19, 2021

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Python (402 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (5,381 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

To my understanding of Papermill, there is currently no option to keep the notebook running / keep the kernel alive and to interact with it.

When a notebook fails, it would be a good time saver to have access to the running notebook to debug using %pdb or to print variables

I barely know Papermill's codebase (and barely know nbclient as well) so it's hard for me to estimate whether it's possible and the work required, but if someone who knows the codebase can give me pointers I could help with the feature 👍

Contributor guide

Research direction
Investigate how Papermill currently executes notebooks and explore options to keep the kernel alive after run by modifying the nbclient execution context to skip kernel shutdown. Start by examining the execute notebook function in papermill's execution module and the nbclient's NotebookClient class.
Tech stack
python
Domain
developer experiencebackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65