Closed kloczek closed 1 year ago
List of modiules installed in build env
Thanks for the report! Do you have any hints to help us understand how sphinx_rtd_theme
is involved in the error tracebacks?
Does this work with an older version of sphinx_rtd_theme
?
What happens if you downgrade Sphinx?
Does this work with an older version of
sphinx_rtd_theme
?What happens if you downgrade Sphinx?
I have no idea and it would a bit hard to test that form me as I've deleted in my rpm packages repo older versions of the sphinx
and sphinx_rtd_theme
.
I'm not sure how it was befor however I'm almost sure that it was not working before but it exact error message was IIRC different and fail was in docutils
code.
Sphinx and docutils do remove and deprecate things - is there a way for you to run this build with an older version of Sphinx?
I'm not seeing the relation to sphinx_rtd_theme here since it's not involved in building man pages. If that's correctly understood, I think you can remove it from the package's build requirements.
My build procedures are badsing on use rpm packages so .. 😞
Other way: are you able to reproduce tht issue in you env?
I'm pretty sure that your traceback says this issue is happening in the manpage builder. As sphinx_rtd_theme is an HTML theme, I don't see the obvious relation.
NotImplementedError: <class 'sphinx.writers.manpage.ManualPageTranslator'> departing unknown node type: CodeAreaNode
Exception occurred:
File "/usr/lib/python3.8/site-packages/docutils/nodes.py", line 2068, in unknown_departure
raise NotImplementedError(
NotImplementedError: <class 'sphinx.writers.manpage.ManualPageTranslator'> departing unknown node type: CodeAreaNode
The full traceback has been saved in /tmp/sphinx-err-0eza3i8a.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
There is something happening with your usage of nbsphinx that causes this.
Please see: https://github.com/sphinx-doc/sphinx/issues/7816
I'm pretty sure that your traceback says this issue is happening in the manpage builder. As sphinx_rtd_theme is an HTML theme, I don't see the obvious relation.
FYI ..
[tkloczko@pers-jacek SPECS]$ grep 'BuildReqires:.*python3dist(sphinx-rtd-theme)' python-*.spec -l | wc -l
105
In other words sphinx-rtd-theme
is working correctly as man page generator in more than 100 other cases.
Interesting. But I'm not sure why any of these 105 packages would use sphinx_rtd_theme for manpages, more likely it's related to html documentation. Looking at some randmly googled source for libcst, I imagine that there's another build command that generates html outputs:
https://src.fedoraproject.org/rpms/python-libcst/blob/f34/f/python-libcst.spec#_79
I'm not usimg Fedora. I have 1.05k packaged python modules of which almost half have documentation nbuild as man pages
[tkloczko@pers-jacek SPECS]$ ls python-*.spec| wc -l; grep %sphinx_build_man python-* | wc -l
1044
485
Man page it is still basic Unix/Linux documentation format.
What I'm saying is that you probably have packages that build manpages - and that Sphinx command is unrelated to sphinx_rtd_theme. You might have another command in your package build that builds HTML documentation using Sphinx's html builder - that's the one that will use sphinx_rtd_theme.
As I wrote I'm only interesyted generate and package man pages as base format (less still is way faster on searching exact phrase on provided documentation than any web browser).
Nevertheless it is interesting that only in one case sphinx-build
command fails when sphinx-rtd-theme
which looks like bug in sphinx
or sphinx-rtd-theme
as it crashes in sphinx-rtd-theme
code.
If you want you can try to reporoduce that issue in your build env by:
git cloen https://github.com/Instagram/LibCST/
cd LibCST
sphinx-build -n -T -b man docs/source build/sphinx/man
to build documenmtation it is not necessry to build that modume to build documentation.
They might have some part of the documentation in LibCST that isn't possible to render with the manpage builder.
Look at the use of .. only:: html
in this segment: https://github.com/Instagram/LibCST/blob/987aff666466b724600a3e1c51f98f8560ceb323/docs/source/conf.py#L223-L232
I suspect your issue is similar to https://github.com/sphinx-doc/sphinx/issues/7816 and you need to find the occurrence in the LibCST documentation where they are using a directive that nbsphinx has invented that doesn't work with the manpage builder.
I still don't see the relation to sphinx_rtd_theme :)
If you want you can try to reporoduce that issue in your build env by:
Yes, indeed that command also gives a solid pointer to where the documentation is broken :tada:
LibCST/docs/source/tutorial.ipynb:: WARNING: unknown node type: <CodeAreaNode: <literal_block...>>
failed
OK thak you 👍
Wil try to open ticket against LibCST
.
Problem
sphinx-build fails with call trace on building man page for
libcst
Give details on your issue.Expected Results
sphinx-build should generate man page.
Environment Info