]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.12] Clarify how topics.py gets created. (GH-106121) (#106579)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 10 Jul 2023 03:42:22 +0000 (20:42 -0700)
committerGitHub <noreply@github.com>
Mon, 10 Jul 2023 03:42:22 +0000 (20:42 -0700)
commit0481b805d6631063887fcbcc27684aa8a2576fae
treee377e650617ae5a41a713ff1a465c7a7f0b0bdb0
parent128a962482ff29325e34b1400c87cc70d509e02a
[3.12] Clarify how topics.py gets created. (GH-106121) (#106579)

Clarify how topics.py gets created. (GH-106121)

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