gh-133905: Fix parsing problems in example code

[cmarqu]

Fix problems in documentation example code snippets that prevent them from being parsed.

• Issue: Some code examples have parsing errors #133905

---

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

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[sobolevn]

Great catch! Thank you!

We should totally add some plugin to parse our examples in the docs.

[sobolevn]

Looks much better to me! Let's wait for other opinions :)

[AA-Turner]

I'm not sure about this. Some of these clearly read better to me without the changes in this PR. I'm also hesistant that the motivation here is just to introduce a third party tool, whereas that tool could just be made more resilient.

A

[bedevere-app]

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

[cmarqu]

The sphinx-codeautolink extension is resilient, but it will not put links in these unparseable code snippets.
The warnings it would produce by default can be handled easily with Sphinx' suppress_warnings.

[terryjreedy]

I would prefer a single line here and for most of the examples. Could do the revision with sed.

Suggested change

	# do something
	...
	... # do something

[cmarqu]

Oops, there was indeed one such occurrence left, fixed. A follow-up PR could reformat all the examples consistently; this PR only works on the places where there were parsing problems.

[github-actions]

This PR is stale because it has been open for 30 days with no activity.