Skip to content

Fix: Restrict jupyter-book version to restore website deployment#291

Merged
FanwangM merged 1 commit intotheochem:mainfrom
dhruvDev23:fix-website-deployement
Feb 23, 2026
Merged

Fix: Restrict jupyter-book version to restore website deployment#291
FanwangM merged 1 commit intotheochem:mainfrom
dhruvDev23:fix-website-deployement

Conversation

@dhruvDev23
Copy link
Contributor

I have noticed that https://selector.qcdevs.org is not opening, and It is giving a 404 Error.

Screenshot 2026-02-22 at 3 36 21 AM

This is because v2.x of jupyter-book introduces a new build system which isn’t compatible with the present Sphinx configuration files, book/content/_config.yml, and book/content/_toc.yml.

Because book/content/requirements.txt doesn’t state a version maximum, pip install -r book/content/requirements.txt installs the latest v2.x, which then prevents the build.

This PR fixes the issue by restricting jupyter-book to a version under <2 in book/content/requirements.txt.

Verification

jupyter-book build ./book/content now runs without a problem, and no longer shows the EISDIR error.

@PaulWAyers PaulWAyers requested a review from FanwangM February 23, 2026 17:37
@PaulWAyers
Copy link
Member

@FanwangM I think @RichRick1 has experience with this.

Copy link
Collaborator

@FanwangM FanwangM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixing the jupyter-book is a neat solution at this stage. We may need to plan for migration to jupyter-book version 2 at some point in the near future.

@FanwangM FanwangM merged commit 74f9ae5 into theochem:main Feb 23, 2026
17 checks passed
@dhruvDev23 dhruvDev23 deleted the fix-website-deployement branch February 23, 2026 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants