Skip to content
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

OldJinjaSuffixWarning for alabaster.css_t in unreleased Sphinx 6.2 #203

Open
bsipocz opened this issue Apr 14, 2023 · 1 comment
Open

OldJinjaSuffixWarning for alabaster.css_t in unreleased Sphinx 6.2 #203

bsipocz opened this issue Apr 14, 2023 · 1 comment

Comments

@bsipocz
Copy link

bsipocz commented Apr 14, 2023

I see the following warning, that our CI treats as error:

Do you foresee any issues with renaming the file?

 Warning, treated as error:
Failed to copy a file in html_static_file: /home/runner/work/sphinx-automodapi/sphinx-automodapi/.tox/py310-test-sphinxdev/lib/python3.10/site-packages/alabaster/static/alabaster.css_t: OldJinjaSuffixWarning("'/home/runner/work/sphinx-automodapi/sphinx-automodapi/.tox/py310-test-sphinxdev/lib/python3.10/site-packages/alabaster/static/alabaster.css_t': the '_t' suffix for Jinja templates is deprecated. If the file is a template, use the suffix '.jinja' instead. For more information, see https://www.sphinx-doc.org/en/master/development/theming.html#static-templates")

https://github.com/astropy/sphinx-automodapi/actions/runs/4694556705/jobs/8322825594#step:8:170

x-ref: astropy/sphinx-automodapi#164

@AA-Turner
Copy link
Member

Alabaster should supress this warning -- if we keep it. Currently the warning only exists in Sphinx HEAD, so for now I'll keep this open, but we won't be renaming the file.

A

@AA-Turner AA-Turner changed the title OldJinjaSuffixWarning for alabaster.css_t OldJinjaSuffixWarning for alabaster.css_t in unreleased Sphinx 6.2 Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants