Thanks, I've replaced some more. Unfortunately the formatting isn't as good, but I think it's acceptable from a maintenance point of view, if there's no better solution?

Before	After

But I've not replaced the hardcoded versions in this section, I don't have a good method for that:

https://docs.python.org/dev/using/mac.html#installing-using-the-command-line

Would an alternative be to have a test/lint ensuring that the version is current? It would be a shame to accept strictly worse aesthetics for a tooling problem.

A

That could work, what sort of thing do you have in mind?

Of course, it would be great if Sphinx directly supported replacements in code blocks ;)

Oh, I've just discoveredparsed literal blocks:

• https://stackoverflow.com/a/27418207/724176
• https://docutils.sourceforge.io/docs/ref/rst/directives.html#parsed-literal

This gives improved formatting, although no syntax highlighting:

Before	After

I struggled with how to handle versions in formatted code when I did the rewrite for 3.13. I'm glad I'm not the only one! If it could be done without a lot of trouble, the linting solution sounds fine until (if ever) there is a better solution with Sphinx / Docutils as this only needs to be updated once a year. But I'll leave it up to you(s).

All commit authors signed the Contributor License Agreement.