quarto-ghp: execnb 0.2 breaks nbdev<3 — `ModuleNotFoundError: No module named 'execnb.nbio'`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
Research direction
Start by locating the quarto-ghp action's install step that runs pip install -Uq "nbdev<3", then reproduce the provided workflow with the current dependency versions. Update the dependency handling so the action no longer raises ModuleNotFoundError: No module named 'execnb.nbio', and verify the workflow completes successfully.
Written by the indexing model from the issue text.
Description
Problem
quarto-ghp@master currently fails with:
ModuleNotFoundError: No module named 'execnb.nbio'
Root cause: The action runs pip install -Uq "nbdev<3", which pulls in the latest execnb (currently 0.2.1). execnb 0.2.0 removed the execnb.nbio submodule, but nbdev 2.x still imports it in nbdev/config.py:
from execnb.nbio import read_nb, NbCell
Affected: Any project using answerdotai/workflows/quarto-ghp@master as of execnb 0.2.0 release.
Reproduction
steps: [uses: answerdotai/workflows/quarto-ghp@master]
Output:
File ".../nbdev/config.py", line 20, in <module>
from execnb.nbio import read_nb,NbCell
ModuleNotFoundError: No module named 'execnb.nbio'
Fix
Either:
- Pin
execnb<0.2in the action's install step alongsidenbdev<3 - Migrate
quarto-ghpto usenbdev>=3(which uses the newexecnbAPI)
Workaround
Projects can work around this today by setting PIP_CONSTRAINT at the job level to a constraints.txt that contains execnb<0.2:
jobs:
gh_pages:
env:
PIP_CONSTRAINT: constraints.txt # contains: execnb<0.2
steps: [uses: answerdotai/workflows/quarto-ghp@master]
- Dominant language
- Python
- Stars
- 44
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AnswerDotAI/workflows
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AnswerDotAI/workflows#78 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
AnswerDotAI/workflows#64 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
AnswerDotAI/workflows#62 ·
All issues in AnswerDotAI/workflows
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·