Skip to content

Commit 0481b80

Browse files
[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 dac1e36) Co-authored-by: Ned Batchelder <[email protected]>
1 parent 128a962 commit 0481b80

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

Doc/tools/extensions/pyspecific.py

+1
Original file line numberDiff line numberDiff line change
@@ -559,6 +559,7 @@ def finish(self):
559559
try:
560560
f.write('# -*- coding: utf-8 -*-\n'.encode('utf-8'))
561561
f.write(('# Autogenerated by Sphinx on %s\n' % asctime()).encode('utf-8'))
562+
f.write('# as part of the release process.\n'.encode('utf-8'))
562563
f.write(('topics = ' + pformat(self.topics) + '\n').encode('utf-8'))
563564
finally:
564565
f.close()

0 commit comments

Comments
 (0)