Please don't backport any of these. Only actual bug fixes should be back ported.

The devguide (https://devguide.python.org/gh-labels/?highlight=backport) says "Generally, backports to the maintenance branches are primarily bugfixes and documentation clarifications." This is a documentation clarification, so it seems fine to backport it.

I am not sure about this. We still keep versionchanged directives for versions >= 3.0 in docs. Even if nobody currently uses Python 3.2, the old (and still working) code can have references to IOError.

That's a good point. IOError isn't mentioned anywhere else in the chunk docs, so I'll revert those changes. (chunk is also now deprecated, so probably not worth worrying about.)

socket.error is documented elsewhere in the module, though, so I think it makes sense to remove the note in the socket docs. Do you agree?

3.9 is now security fixes only so that solved itself. Whether it makes sense to backport to 3.10, in general we are backporting docs changes that apply to older versions as not doing so leads to needless conflicts later on if some bugfix is applied that touches docs. So I'd backport to 3.10, too, as we're already doing for 3.11.

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

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

GH-92969 is a backport of this pull request to the 3.10 branch.

Thanks @ambv!