⬆️ UPGRADE: Upgrade to support sphinx4, remove support for sphinx2#356
⬆️ UPGRADE: Upgrade to support sphinx4, remove support for sphinx2#356
Conversation
|
@chrisjsewell this PR has far fewer changes than #352 as it turns out there don't seem to be a huge number of I have added a string though to
|
|
@chrisjsewell @choldgraf I reconfigured I am wondering if we should:
|
Codecov Report
@@ Coverage Diff @@
## master #356 +/- ##
=======================================
Coverage 87.43% 87.43%
=======================================
Files 12 12
Lines 1337 1337
=======================================
Hits 1169 1169
Misses 168 168
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
|
@chrisjsewell not sure why are expected given the |
.github/workflows/tests.yml
Outdated
| os: [ubuntu-latest] | ||
| python-version: [3.6, 3.7, 3.8, 3.9] | ||
| sphinx: [">=3,<4"] | ||
| python-version: [3.7, 3.8, 3.9] |
There was a problem hiding this comment.
If you are deprecating python 3.6 support, then you need to update setup.cfg
There was a problem hiding this comment.
ah right -- roger that.
Perhaps I won't in the case. This can be done separately if we want to do that as a project.
There was a problem hiding this comment.
the endo of life is in a few months, so it is fine to do so: https://devguide.python.org/#status-of-python-branches
There was a problem hiding this comment.
still not sure why
tests (ubuntu-latest, 3.8, >=2,<3) Expected — Waiting for status to be reported
is expected though. @chrisjsewell I can't see sphinx2 anywhere across the various configs.
There was a problem hiding this comment.
it's part of the branch protection rules
There was a problem hiding this comment.
@chrisjsewell that end of life chart is pretty great. 👍 I might open an issue to EOL python3.6 for December
There was a problem hiding this comment.
it's part of the branch protection rules
Oh -- thanks I would never have checked there :-)
|
OK so I have updated
|
|
@chrisjsewell do you want to be explicit about testing of
|
choldgraf
left a comment
There was a problem hiding this comment.
This in general LGTM! As long as tests are happy then I think we should go for it.
| @@ -0,0 +1,169 @@ | |||
| <document source="with_glue"> | |||
There was a problem hiding this comment.
Should we now expect a new one of these files for every major version of Sphinx that we support?
There was a problem hiding this comment.
@choldgraf the sphinx3 is the same as the old fixture file. There is a minor difference in what sphinx includes in the xml "align='default'" is no longer specified in sphinx4
|
@chrisjsewell do you want to cast an eye over this before it is merged? |
|
thanks @choldgraf for reviewing this. I will merge this tomorrow if there are no further comments. |
|
In the meeting today I think that we agreed that it's time to merge this one and cut a release! 🚀 |
|
Absolutely - I can do that this afternoon. Just tied up with a few other things this morning. |
This PR enables support for
sphinx>=4and drops support forsphinx<=2fixes #338
Updated
testingto:python=3.6topython=3.9againstsphinx3andsphinx4release onubuntu-latestpython=3.9andsphinx4forosx-latestpython=3.7andsphinx3forwindows-latestThis PR adds support for tracking differences between
sphinx3andsphinx4but tracking ofdocutilsversions in the test fixtures is not required at this stage.