-
Notifications
You must be signed in to change notification settings - Fork 61
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
UPGRADE: Sphinx 6.x. #106
UPGRADE: Sphinx 6.x. #106
Conversation
Thanks for submitting your first pull request! You are awesome! 🤗 |
Seeing as Sphinx 6 isn't finalized or released yet, it seems prudent to wait for a release before changing this. Major Sphinx releases have a tendency to upgrade docutils, which has a tendency to break things. |
Works for me. |
Would be great to add support for this as this is blocking PyVista in pyvista/pyvista#3762. |
Seeing that docutils 0.18 and 0.19 have already been released for a while, that should not be a source of issues. Sphinx 6 removed jQuery but I can't find anywhere that sphinx-design uses this? I don't know anything else that could raise concerns here. The release notes are available here: https://www.sphinx-doc.org/en/master/changes.html |
I'm +1 on this, but we'll need to bump the versions to latest of all of the other dependencies in |
@choldgraf you're right!
Seems we need a new release of myst-parser to come out, Sphinx 6 was added yesterday: executablebooks/MyST-Parser#664 |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
==========================================
+ Coverage 90.02% 90.03% +0.01%
==========================================
Files 11 10 -1
Lines 942 933 -9
==========================================
- Hits 848 840 -8
+ Misses 94 93 -1
Flags with carried forward coverage won't be shown. Click here to find out more. see 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There is a new MyST-Parser release available: |
Hey, thanks for the work on this! Linking #118 for reference here, as it is closed by this PR. |
@chrisjsewell or any other collaborator. Can someone trigger the tests and/or review this? |
Updating to myst 1.0 so that we no longer pin Sphinx
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 seems reasonable to me! I updated the MyST Parser as well because that was pinning Sphinx at myst-parser 0.18. I see that tests are happy (the 3.8 failure is because of a codecov upload error, not the test suite), so I'll merge this one!
@choldgraf Thank you very much 🎉. Seems that pre-commit CI needs some upgrading though? |
Any remaining fixes until version bump? |
Nothing blocking, just hours in the day. If others are interested in helping to maintain, merge PRs, cut releases, etc, please let me know! Here's a PR to cut a new release: If the tests are happy then I'll merge and release on github 👍 |
There should not be any fundamental problem with supporting Sphinx 6.x.
To do
Closes #118