9.0.0 release plan

[AA-Turner]

I intend to release Sphinx 9.0.0 soon, perhaps this week (w/c 24 Nov).

9.0.0 will be the last release with support for Python 3.11, in a slight extension to our support policy.

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

The largest change is a substantial rewrite to sphinx.ext.autodoc. See #14089 for a dedicated tracking issue.

The open items on the 9.0 milestone are:

• KeyError: 'writer' with myST-Parser since PR #13676 #13713
• Custom configuration classes break numpydoc #13942

A

cc: @sphinx-doc/developers @sphinx-doc/triagers

[jfbu]

It would be nice for #13713 to get resolved before release, perhaps though it is primarily a downstream issue at MyST-Parser. As it stands, our 9.0.0 breaks compatibility with MyST-Parser. I opened there an issue.

Apart from this, there are no blocking issues on my side, or at least none that I can handle in the near horizon.

[jfbu]

I am sorry about the micmac with milestone, what happened is that I typed on the keyboard while previewing my comment and some keystrokes combination did the milestone removal...

[user27182]

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

Can #13469 be considered for the release?

[jayaddison]

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

I don't think that this is a blocker for release, but: I'd be eager to try to get the recent intermittent/flaky numfig unit test failure fixed -- I can try to find some time for that tomorrow morning.

[jayaddison]

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

I don't think that this is a blocker for release, but: I'd be eager to try to get the recent intermittent/flaky numfig unit test failure fixed -- I can try to find some time for that tomorrow morning.

I've opened an experiment to try to resolve the test flakiness -- I'm uncertain whether it's a genuine fix, and it would require multiple test runs to determine whether it helps -- at: #14100

[Carreau]

May I suggest a pre-releases / nightly ? (nightly for example here https://github.com/scientific-python/upload-nightly-action).

[jayaddison]

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

I don't think that this is a blocker for release, but: I'd be eager to try to get the recent intermittent/flaky numfig unit test failure fixed -- I can try to find some time for that tomorrow morning.

I've opened an experiment to try to resolve the test flakiness -- I'm uncertain whether it's a genuine fix, and it would require multiple test runs to determine whether it helps -- at: #14100

Nope, that pull request did not resolve the problem; the same test has failed again a few moments ago: https://github.com/sphinx-doc/sphinx/actions/runs/19747566759/job/56584758555#step:10:4910

...I'll try to investigate some more.

[jayaddison]

Please let me know if there are any features or bugfixes you would like to have included in the release, or any other matters.

I don't think that this is a blocker for release, but: I'd be eager to try to get the recent intermittent/flaky numfig unit test failure fixed -- I can try to find some time for that tomorrow morning.

I've opened an experiment to try to resolve the test flakiness -- I'm uncertain whether it's a genuine fix, and it would require multiple test runs to determine whether it helps -- at: #14100

Nope, that pull request did not resolve the problem; the same test has failed again a few moments ago: https://github.com/sphinx-doc/sphinx/actions/runs/19747566759/job/56584758555#step:10:4910

...I'll try to investigate some more.

Let's take this off-thread, to be tracked instead by: #14104

[AA-Turner]

I have published a candidate release, Sphinx 9.0.0rc1, to the Python Package Index.

For awareness and/or pre-release testing, cc:

• @agoose77 / @choldgraf (https://github.com/executablebooks/sphinx-book-theme)
• @bsipocz / @pllim / @Cadair (https://github.com/astropy/sphinx-automodapi)
• @drammock / @gabalafou / @trallard (https://github.com/pydata/pydata-sphinx-theme)
• @eli-schwartz / @mgorny (Gentoo)
• @hugovk (https://github.com/python/python-docs-theme)
• @humitos (https://github.com/readthedocs/sphinx_rtd_theme)
• @jarrodmillman / @larsoner (https://github.com/numpy/numpydoc)
• @jbms / @2bndy5 (https://github.com/jbms/sphinx-immaterial/)
• @jdknight (https://github.com/sphinx-contrib/confluencebuilder)
• @joeced (https://github.com/sphinx-contrib/matlabdomain)
• @lucyleeow (https://github.com/sphinx-gallery/sphinx-gallery)
• @mgeier (https://github.com/mgeier/insipid-sphinx-theme/ & https://github.com/spatialaudio/nbsphinx/)
• @pradyunsg (https://github.com/pradyunsg/furo)

A

[eli-schwartz]

Working on it, but why did #13941 add ipython as a dependency?