-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
page_source_suffix not in 1.3.5 #2278
Comments
Seems like it isn't included in the |
This is the commit -- should be backwards compat, and included in releases, I think: 5f6503c |
At this moment, the milestone for v1.4 is put on Feb. 8th. @shimizukawa Let us know about the release plan. |
I'm going to release 1.4 alpha 1 around Feb 14th. I'll send my 1.4 release schedule to sphinx dev ML later. |
Great -- I guess my question is what I would have done differently to get that patch into the 1.3.x release? It's arguably a bug fix for the suffix support, as pages can't tell what markup they were rendered from. |
I assume there was a PR made against the master branch. Bugfix releases are made from the stable branch. |
That said, it is also our responsibility as maintainers to check whether a PR against master should go to stable instead. |
+1 for stable. Surely, |
👍 -- would love to see this get merged into a stable release as soon as possible. Should I open a PR against |
Yes, please. I don't know when @shimizukawa has planned the next 1.3.x release. |
Ah, ok, I'll cherry-pick the commit by #1876 to avoid merge conflict. |
Now stable branch contains a 5f6503c change for page_source_suffix. |
Thanks! |
I added a a while ago adding page_source_suffix to HTML context, so you can tell if you're working on markdown or rst files. It isn't included in 1.3.5:
https://github.com/sphinx-doc/sphinx/blob/1.3.5/sphinx/builders/html.py#L427
It however has been in master for a long time:
https://github.com/sphinx-doc/sphinx/blob/master/sphinx/builders/html.py#L431
How is it not included in any of the releases?
The text was updated successfully, but these errors were encountered: