-
Notifications
You must be signed in to change notification settings - Fork 48
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
latest
doc LaTeX build fails
#475
Comments
Thanks @hakonanes, Carter and I had had a look at this and it seemed non-obvious :( |
My best guess is that pinning the sphinx version should help to fix this? |
I'm leaning towards replacing nbsphinx with Sphinx-Gallery. People can still download the tutorials as notebooks then. What do you think? |
I've reported this issue to the nbsphinx developers. As you say @CSSFrancis, we should try to make our LaTeX build work for now (e.g. by pinning to a Sphinx/nbsphinx version combination that works). We can remove the pinnings once the LaTeX build works again with newer versions. Unless you guys want to switch to Sphinx-Gallery altogether, of course. |
I'm happy with a pin for now and then a patch when a fix comes in if others are? |
The previous successful LaTeX build was in December with the same nbsphinx that fails. Only reverting the Sphinx version to 6.2 or 5.3 or the nbsphinx version to 0.8 doesn't fix the LaTeX build. I think this requires a MWE to find the cause of the error. |
@hakonanes and @pc494 Is there anything different about the |
The only difference I can think of is related to the tags? Edit: I didn't look very closely. The error is thrown when trying to build the pdf and succeeds when building the html, it seems like it is just an issue with the pdf build. Do we need a pdf build? I doubt that it is used and if it causes problems it might be nice to just remove that so we can get things to work. |
Yes, we should provide the docs in PDF format. But I don't think the failing LaTeX build should hold up the 0.12 release. I suggest we live with the failing docs badge as a reminder to fix this. |
@hakonanes Sounds fair. I think that moving to sphinx gallery for everything is probably the best thing to do as that has a cleaner git history and works a bit better than Jupyter notebooks. |
The feature we lose switching to SG is saving outputs in the notebook, so RTD doesn't have to run the tutorial. That is crucial for some of our tutorials. We have to reconsider those tutorials before switching. I forgot about that... |
@hakonanes can you narrow it down a bit. Does running nbconvert on the Jupyter notebooks throw an error not in the sphinx workflow? Can you stop some of the notebook conversions to narrow down which one is causing the issue. Then can we figure out what bit of latex is causing issues? I haven't been able to reproduce this on my laptop. |
Is it possible that we aren't doing a great job of installing the latex packages for converting to pdf. https://nbconvert.readthedocs.io/en/latest/install.html#installing-tex. It seems like we should be installing the TeX Live package as I don't think that pandoc natively supports conversion to pdf (https://pandoc.org). This is just me spitballing though. |
Are you running the command run by RTD? With I'll try to create an MWE for us to test with and also to provide to nbsphinx maintainers.
Perhaps. But, I don't think that's the issue here, given the LaTeX build ran fine before. pandoc is required by nbsphinx for "converting Markdown to something Sphinx can understand". |
This is now temporarily fixed in #495. |
Builds from the
latest
branch fail: https://beta.readthedocs.org/projects/orix/builds/23890511/.It's nbsphinx that throws an
AssertionError
in itsnbsphinx/__init__.py
in a function nameddepart_codearea_latex
:No clear error message.
Versions:
I'll try to reproduce locally and see if I can fix this.
Should be fixed before we release v0.12.
The text was updated successfully, but these errors were encountered: