Conversation
This comment was marked as spam.
This comment was marked as spam.
amotl
left a comment
amotl
left a comment
There was a problem hiding this comment.
Thank you for mitigating this. I don't have objections about the suppression of the warning, but would like to keep reporting and bookkeeping procedures sound.
| # 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, | ||
| ) | ||
|
|
There was a problem hiding this comment.
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
-
Would it just be about asking for a new release, or does it need patches? 2 ↩
-
Maybe https://github.com/executablebooks/MyST-NB/pull/706 fixed it already? ↩
There was a problem hiding this comment.
Ups! Wrong copy/paste. Good catch 👍
There was a problem hiding this comment.
There is a PR from Dec open that seems dormant: executablebooks/MyST-Parser#1079
There was a problem hiding this comment.
(updated with correct link directly in main)
2 participants
About
Disable all the deprecation warnings as the build log is flooded by them. E.g. here.