Skip to content

Fix: Disable Myst deprecation warnings #704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bmunkholm merged 1 commit into from
Feb 12, 2026
Merged

Fix: Disable Myst deprecation warnings #704

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions src/crate/theme/rtd/conf/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@
# with Crate these terms will supersede the license and you may use the
# software solely pursuant to the terms of the relevant commercial agreement.
import os
import warnings

from crate.theme import rtd as theme
from crate.theme.rtd import __version__
Expand Down Expand Up @@ -183,6 +184,14 @@
linkcheck_retries = 3
linkcheck_timeout = 15

# Suppress myst-nb deprecation warnings until fixed upstream.
# https://github.com/executablebooks/MyST-NB/issues/645
warnings.filterwarnings(
"ignore",
message=r".*myst_nb\.sphinx_\.Parser\.env.*",
category=DeprecationWarning,
)

Comment on lines +187 to +194
Copy link
Member

@amotl amotl Feb 12, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

I think that is the wrong issue, and it is already closed: It reported about the sphinx.util.import_object symbol being deprecated.

May I ask you to please report your specific observation about the myst_nb.sphinx_.Parser.env symbol to the upstream project 1 and reference the new ticket here? 🙏

Footnotes

  1. Would it just be about asking for a new release, or does it need patches? 2 ↩

  2. Maybe https://github.com/executablebooks/MyST-NB/pull/706 fixed it already? ↩

Copy link
Contributor Author

@bmunkholm bmunkholm Feb 12, 2026

Choose a reason for hiding this comment

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

Ups! Wrong copy/paste. Good catch 👍

Copy link
Contributor Author

@bmunkholm bmunkholm Feb 12, 2026

Choose a reason for hiding this comment

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

There is a PR from Dec open that seems dormant: executablebooks/MyST-Parser#1079

Copy link
Contributor Author

@bmunkholm bmunkholm Feb 12, 2026

Choose a reason for hiding this comment

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

(updated with correct link directly in main)

# -- Options for MyST -------------------------------------------------
myst_heading_anchors = 3
myst_enable_extensions = [
Expand Down