-
Notifications
You must be signed in to change notification settings - Fork 326
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
Fix several CSS elements and bugs for Sphinx 5 #818
Conversation
I'd appreciate a review from somebody on this, at least at the level of how the visual style looks in the end result. It would be nice to get support for Sphinx 5 in the next release! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good! I didn't spot anything odd-looking in the rendered docs that isn't already that way on main
/ devdocs. Code changes look reasonable, just a couple small comments.
thanks @drammock ! I implemented both suggestions 👍 I like your footnote spacing better :-) |
Co-authored-by: Daniel McCloy <dan@mccloy.info>
Ready for review / mergeI just rebased this one on If we don't notice any, I suggest that we merge this in and make an |
That's what happens when it runs out of horizontal space...not sure how to deal with that yet haha. You could try |
This is reported in #845, further discussion of this problem can go there |
By the way - I welcome others to push changes to this PR branch, I am really busy with a grant deadline for the next few days and would like to get a new release out soon if possible because there are many nice new changes to add! |
OK I think that I fixed the sidebar one in #849 Want to try that out @tupui ? I also looked at our Sphinx Design page, and don't see any messed up padding or extra lines, so I'm not sure what to do there. Maybe we can track that and follow up in a new issue. I'm going to merge this, and cut a new RC so that we can have people test out |
@choldgraf I just tried |
Can you provide a link or open up an issue with a reproducible set of steps? I can't figure out how to reproduce on my side |
@choldgraf you can use this PR: scipy/scipy#16660 To build the SciPy and the doc (build should take around 3 mins with 6 cores, then 5 mins for the doc itself):
Thanks for looking into this Chris! Let me know if you want me to try something to help. |
Hmmm you don't have a Read the Docs PR preview to use? I'm sorry but I don't have time to download and build the scipy docs locally, I'm on vacation right now :-/ |
Oh sure no worries. If it's a build that you need, I can update the current PR I have so that it builds with the RC. All that can wait until you are back. FYI SciPy 1.9 got released this WE. I will post here the link once the build is done (just started). |
Ok sounds good - I think we should open a separate issue to track this instead of reusing this PR. Can you do that and provide a link to the reproducible example there? Do you think this should block the next release if the theme? |
Sure, I will open a new issue (see #854). What I am seeing now that is more of an issue for the next release is that build time significantly increased. I noticed this as well locally but thought it was a hiccup at first. But on the CI it seems to be consistently happening (timeout, not even finishing). |
Can you please open new issues for anything? 🙂 |
## Footnotes | ||
|
||
Here's one footnote[^1] and another footnote [^2] and a named footenote[^named], symbol [^*]. | ||
|
||
[^1]: Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. | ||
[^2]: Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. | ||
[^named]: Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. | ||
[^*]: Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. Foo bar foo bar. | ||
|
||
## Version changes | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't look correct? It is a whole section inserted into the middle of another one (Admonition sidebars). It also restores the Version changes
heading that was removed in https://github.com/pydata/pydata-sphinx-theme/pull/836/files#diff-0607a043e4091f4e22ccc62684762b4a6b00d03e638ff096277e7f4dde9cba77L97, but none of its section content.
This PR touches the CSS in several different places, with the goal of making sure it works with Sphinx 5 / docutils .18+. It also fixes a few bugs in the process as well as a few DRY improvements by re-using SCSS variables.
This fixes all of the things things mentioned in the issue below, closes #817 .
In addition, there were a few other things I fixed up along the way. They were noticeable when I was testing locally with docutils .18/sphinx 5, but I'm not sure exactly which were due to the version change and which were just things to improve in general, so it's kind-of a mishmash of stuff.