[issue22593] Automate update of doc references to UCD version when it changes.

Change by Ned Deily : -- assignee: -> docs@python components: +Documentation nosy: +docs@python, mdk versions: +Python 3.9 -Python 3.5 ___ Python tracker ___

[issue22593] Automate update of doc references to UCD version when it changes.

Noah Massman-Hall added the comment: I ended up doing exactly what I said would probably be needed, and wrote a small sphinx extension that handles this. I kept the same reST substitution syntax, but I'm parsing for '|ucd_version|' as the source files are read in and just replacing it with

[issue22593] Automate update of doc references to UCD version when it changes.

Change by Noah Massman-Hall : -- pull_requests: +17186 pull_request: https://github.com/python/cpython/pull/17748 ___ Python tracker ___

[issue22593] Automate update of doc references to UCD version when it changes.

Change by Noah Massman-Hall : -- pull_requests: -17155 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22593] Automate update of doc references to UCD version when it changes.

Change by Noah Massman-Hall : -- keywords: +patch pull_requests: +17155 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/17710 ___ Python tracker

[issue22593] Automate update of doc references to UCD version when it changes.

Noah Massman-Hall added the comment: I took a crack at the rst side of this, to see if I could reduce it to just one easy to parse for line in each file that needs to be modified. Yeah, not so easy. Substituting text in rst isn't hard, you just insert '|ucd_version|' where the version

[issue22593] Automate update of doc references to UCD version when it changes.

Batuhan added the comment: I want to work on this. What do you think about using include directive and include a static file like UCD_VERSION.txt in the documents? makeunicodedata.py can write the current version every run to UCD_VERSION.txt -- nosy: +BTaskaya

[issue22593] Automate update of doc references to UCD version when it changes.

New submission from R. David Murray: As noted by Alexander in issue 18176, we often forget to update the UCD references in the docs when we switch to a new version. That issue added notes to the makeunicodedata script to list the places that need to be changed; however, it would be even