Docs: Avoid a DeprecationWarning in pyspecific.py when running with Sphinx >=6.1

[AlexWaygood]

Importing status_iterator from sphinx.util rather than sphinx.util.display causes a DeprecationWarning to be emitted if you're running with Sphinx >= 6.1. We still support the CPython docs being built with older versions of Sphinx that don't yet have sphinx.util.display, however, hence the try/except ImportError block. You can see this deprecation warning here (though the doctest is also failing on that job, I think for unrelated reasons): https://github.com/python/cpython/actions/runs/5297276975/jobs/9588952949?pr=105882

---

📚 Documentation preview 📚: https://cpython-previews--105886.org.readthedocs.build/

[hugovk]

Please could you add comments similar to hugovk@c4a84f6 so we know when to remove the old bit?

And shall we tidy up some older imports that weren't commented, like in hugovk@fb4e1cc?

(I forgot to open a PR for these!)

[AlexWaygood]

Please could you add comments similar to hugovk@c4a84f6 so we know when to remove the old bit?

And shall we tidy up some older imports that weren't commented, like in hugovk@fb4e1cc?

(I forgot to open a PR for these!)

Oh, yours is better than mine, do you just want to open a PR (or two) with your patch(es)? :)

[hugovk]

It's fine, we can do it here, we don't want to run out of PR numbers! 🙃

You could add a Co-authored-by if you like, but I don't mind either way.

[JelleZijlstra]

Should we backport this? Might make us run out of PR numbers sooner.

[hugovk]

Yes, let's backport it. (We've saved one PR number, so can invest in two more.)

[arhadthedev]

Might make us run out of PR numbers sooner.

We rather need to waste IDs on an industrial scale to get cpython#666666 faster 😉

[miss-islington]

Thanks @AlexWaygood for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12.
🐍🍒⛏🤖

[bedevere-bot]

GH-106010 is a backport of this pull request to the 3.12 branch.

[bedevere-bot]

GH-106011 is a backport of this pull request to the 3.11 branch.