Skip to content

chore: enable -W strict sphinx build gate [hold for lock bump]#176

Draft
markgeejw wants to merge 1 commit into
developfrom
chore/strict-sphinx-build
Draft

chore: enable -W strict sphinx build gate [hold for lock bump]#176
markgeejw wants to merge 1 commit into
developfrom
chore/strict-sphinx-build

Conversation

@markgeejw

Copy link
Copy Markdown
Collaborator

What

Turns the doc build strict: sphinx-build -W --keep-going. Warnings become errors so doc-link rot and docs/client-API drift fail the build instead of silently shipping (e.g. an empty autodoc stub for a missing class).

⚠️ Do not merge yet — draft on purpose

This must merge together with the pixi.lock bump to an openprotein-python release that contains:

  • PR #222 (docstring/annotation fixes), and
  • ESMIF1Model.

Against the currently pinned 0.13.0, -W fails on 13 pending warnings (2 list signature failures, 3 ESMIF1Model import, 4 docstring indentation, 5 session.x? highlighting) — all already fixed on the client's develop, just not on PyPI. Merging before the lock bump would break the develop build and its dev-site deploy.

Verification

Built with -W against the client's develop (editable install): clean except the two untracked WIP notebooks (binder.ipynb, membrane.ipynb) that don't exist in a clean CI checkout. So CI's -W build will be green once the lock points at a release with #222 + ESMIF1Model.

Merge sequence

  1. Cut openprotein-python release (with #222 + ESMIF1Model).
  2. In a single PR (or this branch, rebased): pixi update openprotein-python + commit pyproject + pixi.lock.
  3. Mark this PR ready and merge.

Promotes sphinx warnings to errors (--keep-going to still report all in one
pass) so doc-link rot and docs/client-API drift fail the build.

HOLD: do not merge until openprotein-docs's pixi.lock is bumped to an
openprotein-python release containing the docstring fixes (PR #222) and
ESMIF1Model. Verified clean against the client's develop branch; against the
currently pinned 0.13.0 this gate fails on 13 pending warnings.
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.

1 participant