@@ -53,7 +53,7 @@ We are currently in branch 3.10, and we want to update the strings from 3.11.
53
53
pip install -r requirements.txt
54
54
55
55
56
- #. Create the .po files from the new source code. This will generate all the .po files for version 3.8 ::
56
+ #. Create the .po files from the new source code. This will generate all the .po files for version 3.11 ::
57
57
58
58
SPHINX_GETTEXT=True sphinx-build -j auto -b gettext -d _build/doctrees . ../python-docs-es-pot
59
59
@@ -69,8 +69,8 @@ We are currently in branch 3.10, and we want to update the strings from 3.11.
69
69
#. At this point, all the `.po ` files will have a different comment on each translation phrase,
70
70
for example::
71
71
72
- -#: ../Doc/whatsnew/3.9 .rst:3
73
- +#: ../python-docs-es/cpython/Doc/whatsnew/3.9 .rst:3
72
+ -#: ../Doc/whatsnew/3.11 .rst:3
73
+ +#: ../python-docs-es/cpython/Doc/whatsnew/3.11 .rst:3
74
74
75
75
As you can see, it added the path of the local repository, but you can
76
76
remove it from it with this regular expression::
@@ -91,3 +91,11 @@ We are currently in branch 3.10, and we want to update the strings from 3.11.
91
91
you will find many warnings that needs to be fixed before the push
92
92
of the new branch is done. So prepare a cup of any hot beverage
93
93
and fix them.
94
+
95
+
96
+ Once the process is completely and you are happy with the results,
97
+ there are a few extra steps to finish the process::
98
+
99
+ #. Upgrade GitHub Actions to use Python 3.11
100
+
101
+ #. Update Read the Docs project to use 3.11 in the build and also as default branch/version
0 commit comments