We are currently in branch 3.10, and we want to update the strings from 3.11.

1. Make sure you are in a clean state of the branch 3.10

2. Create a new branch

3. Fetch the latest commit of 3.10 branch:

   cd cpython/
   git fetch --depth 1 origin 69b6b56d857440183e227ca0b10c84bca4239985
   

   Note

   you could also base the hash on the 'git tag' from the desired version: git checkout tags/v3.11.0 -b 3.11 considering that 3.11 doesn't exist locally.

4. Checkout that commit locally:

   git checkout 69b6b56d857440183e227ca0b10c84bca4239985
   

5. Update the branch on the Makefile and check the requirements.txt from the cpython repository, to see if upgrades on the modules like sphinx is needed.

6. Verify that the docs build with the new versions you changed from requirements.txt mainly the sphinx version.

7. Commit the update of the submodule change:

   git add cpython
   git commit -m "Update the cpython submodule"
   

   Note

   This is important, so the later make build step will not reset the cpython submodule to the previous hash on the old branch.

8. Clean possible garbage (form previous builds):

   rm -rf _build ../python-docs-es-pot cpython/Doc/CONTRIBUTING.rst cpython/Doc/upgrade-python-version.rst
   

9. Create a virtual environment and install the dependencies of the project:

   python -m venv env
   source env/bin/activate  # Windows: env\Scripts\activate.bat
   pip install -r requirements.txt
   

10. Create the .po files from the new source code. This will generate all the .po files for version 3.8:

    SPHINX_GETTEXT=True sphinx-build -j auto -b gettext -d _build/doctrees . ../python-docs-es-pot
    

    Note

    In ../python-docs-es-pot directory, we will have the new .pot files with new strings from 3.11 branch. All these strings will be untranslated at this point.

11. Now, we update our translated files form the source language (English) with new strings:

    sphinx-intl update --language es --pot-dir ../python-docs-es-pot --locale-dir cpython/locales/
    

12. At this point, all the .po files will have a different comment on each translation phrase, for example:

    -#: ../Doc/whatsnew/3.9.rst:3
    +#: ../python-docs-es/cpython/Doc/whatsnew/3.9.rst:3
    

    As you can see, it added the path of the local repository, but you can remove it from it with this regular expression:

    sed -i **/*.po -e "s|python-docs-es/cpython/||g"
    

    ..note:: if you have your local repository cloned with a different name,

    please make sure to adapt the expression.

13. Pass powrap to make the column widths consistent:

    powrap --modified
    

14. Prepare for fireworks! Now it's time for an initial build:

    make build
    

    you will find many warnings that needs to be fixed before the push of the new branch is done. So prepare a cup of any hot beverage and fix them.