- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[v2.0.0b1] TemplateNotFound #6186
Comments
About the message not being vebose enough (just |
Is this caused by string value in Lines 1089 to 1095 in 42c8fbd
|
Yes but when I'm upgrading a project from 1.8.5 to 2.0.0 I'm not reading the 1.7.0b1 changelog :] |
Should we mention the deprecated feature also on removal? We'll drop all deprecations in 1.7.x series on next major release. |
I think so, like I propose in #6187 (don't know if there are others), to be sure people just reading the release changes (like I did) get it right. Also because this one (due to the Jinja2 error message not being comprehensive enough) is really tricky to diagnose. |
Hmm... it means nobody reads "deprecated" section and command line warnings... |
Yes, the sad reality :( But I have an excuse \o/ my "command line warnings" are scattered into 31 logs files, producing 4068066 lines of log daily (thanks to latex warning mainly), so I only read them when really needed. But yes that's sad I didn't spotted the For the Sphinx 2 upgrade I read the CHANGES file today (but I expect almost nobody does it), but only the 2.0 section, not mentionning html_sidebar þ |
In 2.0.0, we'll mark large amount of code as deprecated. It means they will be removed in future version (maybe in 4.0.0). I feel copying them to CHANGES on future version is annoying. Lines 174 to 257 in e6cc18c
How about adding an entry like "Drop features deprecated in 1.7.x " instead? |
|
Add an incompatible change entry (refs: #6186)
done n #6195. |
Otherwise the docs-lld-html target fails to build using recent Sphinx with the following not very helpful error message: An error happened in rendering the page index. Reason: TemplateNotFound() It turns out the values in the html_sidebars dictionary always need to be lists now. See sphinx-doc/sphinx#6186
Otherwise the docs-lld-html target fails to build using recent Sphinx with the following not very helpful error message: An error happened in rendering the page index. Reason: TemplateNotFound() It turns out the values in the html_sidebars dictionary always need to be lists now. See sphinx-doc/sphinx#6186
Otherwise the docs-lld-html target fails to build using recent Sphinx with the following not very helpful error message: An error happened in rendering the page index. Reason: TemplateNotFound() It turns out the values in the html_sidebars dictionary always need to be lists now. See sphinx-doc/sphinx#6186
Hi!
Whild building cpython documentation for cpython 2.7 with sphinx 2.0.0b1 I'm having a
TemplateNotFound
error without any other indication.Breaking in the code helps me a bit, it's a
page.html
that is missing.cc @tk0miya not sure if the issue is my side or sphinx side but as we're near the 2.0.0 release I prefer mentionning you on this issue.
To Reproduce
see at the end:
Expected behavior
No build error OR a verbose message.
Environment info
More info
With v1.8.5 it works.
Stacktrace:
Exploring the stacktrace near
if next
I'm seeing:In the
{%- if next %}
context I'm seeing:OK so this is:
So this just have to be documented in the
CHANGES
files, in theIncompatible changes
section.The text was updated successfully, but these errors were encountered: