Deprecation proposal: legacy Jinja template suffixes ('_t' vs '.jinja') #14266
jayaddison
started this conversation in
Feature requests and ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For a long time (since 2f18cc9 in Y2009, ~17 years ago), Sphinx has supported template evaluation of
staticfiles within projects. In particular, static files that have a_tsuffix are evaluated as templates, and Jinja has always been the rendering engine used to evaluate them.From #11916, first released with Sphinx v7.4.0 in July of Y2024 (~18 months ago), Sphinx has supported evaluation of template files when they have a
.jinjafilename extension, in addition to retaining the existing support for templates with the suffix_t.Sphinx itself has migrated its internal templates to use the
.jinjaextension instead - but not all downstream projects, extensions and so on will have done yet.Can we begin adding deprecation notices when files with the legacy
_tsuffix are evaluated?Beta Was this translation helpful? Give feedback.
All reactions