]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.11] Clarify how topics.py gets created. (GH-106121) (GH-106580)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Tue, 22 Aug 2023 19:23:55 +0000 (12:23 -0700)
committerGitHub <noreply@github.com>
Tue, 22 Aug 2023 19:23:55 +0000 (19:23 +0000)
commitfadf8a032b8b602ed2681aa912ceab01d095fd8f
treeb61df0e0412dc906388222c33232e8e87bc1d736
parent9d7f2705b51eb7a4c48799ea16786f4a69f57dc5
[3.11] Clarify how topics.py gets created. (GH-106121) (GH-106580)

When changing docs, it was easy to find text in topics.py, and I
wondered whether I was supposed to edit it.  Thankfully, the top of the
file says it's auto-generated, so I knew I didn't have to edit it. But I
didn't know what started the auto-generation process.

It's part of the release process, so I'll leave a note here for future
editors.
(cherry picked from commit dac1e364901d3668742e6eecc2ce63586330c11f)

Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
Doc/tools/extensions/pyspecific.py