emacs-jupyter/jupyter

Ignore archived subtrees when `jupyter-org-execute-to-point`

Open

#177 opened on Sep 1, 2019

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Emacs Lisp (106 forks)auto 404
enhancementhelp wantedorg

Repository metrics

Stars
 (1,028 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

#+property: header-args:jupyter-python :session test :async yes :exports both :tangle test.py


* Heading1

#+begin_src jupyter-python
print('Heading1')
#+end_src

* Heading2                                                          :ARCHIVE:

#+begin_src jupyter-python
print('Heading2') # Should we ignore this block?
#+end_src

* Heading3

#+begin_src jupyter-python
print('Heading3') # run `jupyter-org-execute-to-point` here
#+end_src

When a subtrees is internal archived, shall we ignore any evaluation on it? How do you think about it?

Contributor guide

Research direction
Start by tracing `jupyter org execute to point` to understand how it identifies code blocks for evaluation. Then examine how org mode marks archived subtrees (the ARCHIVE tag) and determine a way to skip those blocks during execution.
Tech stack
None
Domain
tooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Emacs LispOrg modeGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70