Open astrojuanlu opened 1 year ago
Another alternative, depending on how much control you have over your build process, is to use the -w flag and then cat
the file out after the build process is done.
You surely mean lowercase -w
:) but this is a great tip, thanks @jdillard!
Too bad support for custom build.commands
on Read the Docs is still in beta https://docs.readthedocs.io/en/stable/build-customization.html#override-the-build-process but I'll revisit this idea in a few months
ha whoops (ChatGPT isn't the only one that hallucinates), fixed it! Always happy to see the improvements RTD is making!
Is your feature request related to a problem? Please describe. I'm always frustrated when my Sphinx builds fail because of warnings, and it's difficult to locate said warnings.
End of output looking similar to:
My trick is usually to
Ctrl/Cmd+F
forwarning:
, filter through the noise, and try to locate the actual warnings. But it's really annoying and most Sphinx users don't know how to do this and get frustrated, since the logs are usually quite large.This has been going on forever, but I found this problem again at https://github.com/kedro-org/kedro-plugins/issues/134 so I decided to open a feature request here.
Describe the solution you'd like Sphinx repeating at the end of the logs what warnings caused the build to fail. Something like:
Describe alternatives you've considered One alternative could be not repeating the warnings, but giving the user a hint of how to look for them. Something like:
But I think this is suboptimal.
Additional context Add any other context or screenshots about the feature request here.