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.
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
assert 'Verbatim' in lines[0] #9458
Comments
I think this is the same as spatialaudio/nbsphinx#584. As mentioned there, the problem exists since #9166. This issue could be either fixed here or in @dham Do you have an idea how to best solve this? |
As commented at spatialaudio/nbsphinx#584, the #9166 transforms container classes into LaTeX environment. This upsets the nbsphinx.depart_codearea_latex(), as first line is not as expected. Simply removing from this procedure the two assert seems to solve the issue, as the output LaTeX code is then valid. The #9166 provides opportunity to abstract away from output latex the latex additions done by the nbsphinx code and put them into suitable |
sorry I meant |
To temporarily fix sphinx-doc/sphinx#9458
I see that issue spatialaudio/nbsphinx#584 which is related to this has been merged and closed. Does this mean it will be fixed in the next |
No, it will be fixed in the next nbsphinx's release instead of Sphinx. I think there is nothing to do on Sphinx side. So I'm closing this. |
Yes indeed. I've just made a new |
Confirm upgrading to 0.8.7 solved this, thanks for the fix |
Describe the bug
Upgrading
sphinx
from 4.0.3 to 4.1.0 raises annbsphinx
exception when building docs in ReadTheDocs:writing... failed
How to Reproduce
Error happens in ReadTheDocs build so not sure how to reproduce. Building locally works fine:
https://github.com/awslabs/aws-data-wrangler/blob/main/building/build-docs.sh
Expected behavior
No response
Your project
https://github.com/awslabs/aws-data-wrangler/tree/main/docs
Screenshots
No response
OS
Catalina
Python version
3.9
Sphinx version
4.1.0
Sphinx extensions
sphinx==4.0.3 sphinx_bootstrap_theme==0.7.1 nbsphinx==0.8.6 nbsphinx-link==1.3.0
Extra tools
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: