@@ -39,6 +39,12 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
39
39
.. note:: This is important, so the later ``make build`` step will not reset
40
40
the cpython submodule to the previous hash on the old branch.
41
41
42
+ #. Create a virtual environment and install the dependencies of the project::
43
+
44
+ python -m venv env
45
+ source env/bin/activate # Windows: env\Scripts\activate.bat
46
+ pip install -r requirements.txt
47
+
42
48
#. Verify that the docs build with the new versions you changed from
43
49
``requirements.txt `` mainly the sphinx version::
44
50
@@ -53,21 +59,14 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
53
59
54
60
#. Clean possible garbage (form previous builds)::
55
61
56
- rm -rf _build ../python-docs-es-pot cpython/Doc/CONTRIBUTING.rst cpython/Doc/upgrade-python-version.rst
62
+ rm -rf _build ../python-docs-es-pot cpython/Doc/CONTRIBUTING.rst cpython/Doc/upgrade-python-version.rst reviewers-guide.rst
57
63
58
64
.. note::
59
65
60
66
The 'python-docs-es-pot' is a temporary directory that is created
61
67
in the next step. It's included here because it might be a leftover
62
68
from previous attempts on your machine.
63
69
64
- #. Create a virtual environment and install the dependencies of the project::
65
-
66
- python -m venv env
67
- source env/bin/activate # Windows: env\Scripts\activate.bat
68
- pip install -r requirements.txt
69
-
70
-
71
70
#. Create the .po files from the new source code. This will generate all the .po files for version 3.11::
72
71
73
72
SPHINX_GETTEXT=True sphinx-build -j auto -b gettext -d _build/doctrees . ../python-docs-es-pot
@@ -114,9 +113,16 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
114
113
of the new branch is done. So prepare a cup of any hot beverage
115
114
and fix them.
116
115
117
- Once the process is completely and you are happy with the results,
118
- there are a few extra steps to finish the process::
116
+ **Once the process is completely and you are happy with the results,
117
+ there are a few extra steps to finish the process **
118
+
119
+ #. Upgrade GitHub Actions to use Python 3.12, by updating Python version to 3.12 in the ``.github/workflows/main.yml `` file.
119
120
120
- #. Upgrade GitHub Actions to use Python 3.12
121
+ #. Update the *Read the Docs * project to use 3.12 in the build and also as default branch/version.
122
+
123
+ #. Commit all the newly created files locally.
124
+
125
+ #. Create branch 3.12 in the repository in order to merge changes there.
126
+
127
+ #. Inside the github project settings, set 3.12 branch as the default branch for the repository.
121
128
122
- #. Update Read the Docs project to use 3.12 in the build and also as default branch/version
0 commit comments