Why are we backporting this to 3.4? 3.4 is in security-fix mode so docs aren't updated or built. This doesn't seem to qualify as a security issue.

We don't build docs for security-fix Pythons?

No, only those in maintenance mode. We don't accept doc fixes for security mode branches unless they have to do with a security fix.

http://cpython-devguide.readthedocs.io/devcycle.html#security-branches

I thought it was odd that the branch wasn't even protected by CI checks. Looks like merges to 3.4 aren't prohibited by anything else either. Is it worth reverting? (It's not harmful.)

I think they are protected, you're required to be a member of the @python/python-release-managers team.. which you are :)

I believe the branch is protected but you (@warsaw) are in the release manager group so you are able to push things there.

I take that back: they probably are rebuilt if any changes were pushed to the branch. But they're not supposed to be unless the release manager approves as a security fix.

Yeah, this particular change isn't a big deal but, on the other hand, there are likely other deprecations and doc updates that would be helpful to 3.4 doc readers but which haven't been backported per policy. I think we shouldn't make a habit of it :)
@larryhastings

Maybe we can adopt python/core-workflow#32 to automatically add the relevant release manager as either the assigned person or request a review from them on branches that are security only. It'd require a bit of coding though.