Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

quarto-ghp: execnb 0.2 breaks nbdev<3 — `ModuleNotFoundError: No module named 'execnb.nbio'`

Open
#77 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd

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:

  1. Pin execnb<0.2 in the action's install step alongside nbdev<3
  2. Migrate quarto-ghp to use nbdev>=3 (which uses the new execnb API)

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AnswerDotAI/workflows

All issues in AnswerDotAI/workflows

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.