-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
PythonFileReporter: do not expect files without a filename extension to contain Python code #1489
Conversation
Awaits sphinx-doc/sphinx#11165 (or similar) |
@nedbat is this still valid? |
It's completely possible that it'll be made redundant by other changes, @ProsperousHeart - it's a fairly innocuous warning message that most people probably won't notice (and likely rarely indicates a genuine problem). That said: I (for no good reason) have the time and energy to follow it, even if it takes months or years, so for me it remains relevant. It's less like the Sagrada Familia and more like a small signpost that's misaligned on a minor countryside road; we're aware of it and it can be fixed at some point. (that analogy doesn't quite make sense, because in this case we're dependent on other signposts changing elsewhere.. it's an effort to explain it, though 🤷) |
(a small note to mention that I continue to be interested in progressing this at some point. roughly speaking, the things on my tasklist ahead of this are: a bunch of Sphinx |
The Sphinx linkcheck-related changes I had in mind have been merged and release in Sphinx v7.1.0 - I'm going to wait for another week or two to allow time for any feedback and bugreports to arrive, and then I'll get started again on updating the Jinja template suffix logic... and then after that is complete, then this will be ready for reconsideration. |
…to contain Python code
…o be evaluated using Python code.
c6a0f0c
to
5c3e420
Compare
I'm not fond of saying that ".jinja" means Python. As #1488 shows, the Python code made by Jinja will be named whatever the original template file was called. So it could be ".j2" or ".rst_t", etc. |
Yep, that makes sense. I'll revert 69e6ef0, also bringing the branch back into alignment with the issue description and this pull request's title. |
…pected to be evaluated using Python code." This reverts commit 69e6ef0.
As I've mentioned in a bugreport comment a few moments ago, I don't think I had understood a detail about the extent of the requirement to support filenames without dotted suffixes - and so I think that this should indeed be closed. My apologies for being defensive about closing it; at the time I felt that this would be a long process but one that could be handled with co-ordination and updates solely in Sphinx. |
Possible fixup; could resolve #1488 (if that's confirmed to be a bug worth addressing).