migrate to python 3.13

Author: sofide

.github/workflows/main.yml

@@ -23,10 +23,10 @@ jobs:
           fetch-depth: 2
 
       # Instalación de dependencias
-      - name: Preparar Python v3.11
+      - name: Preparar Python v3.13
         uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           cache: "pip"
       - name: Configura dpkg/apt para ejecutarse de manera eficiente
         uses: abbbi/github-actions-tune@v1

.github/workflows/pr-comment.yml

@@ -18,10 +18,10 @@ jobs:
         with:
           ref: ${{ github.event.pull_request.head.sha }}
           persist-credentials: false
-      - name: Preparar Python v3.11
+      - name: Preparar Python v3.13
         uses: actions/setup-python@v5
         with:
-          python-version: "3.11"
+          python-version: "3.13"
           cache: "pip"
       # checkout these files from the base branch to guarantee they haven't been
       # modified by the PR

.overrides/faq.rst

@@ -19,7 +19,7 @@ Tenemos un `grupo de Telegram`_ en el que hay mucha gente que te puede ayudar.
 Uno de los chequeos que realiza nuestro servidor de github cada vez que hacemos
 un pull de request es un test de corrección ortográfico usando la herramienta
 pospell. Pospell puede ser instalada en tu entorno de Python empleando pip
-(https://pypi.org/project/pospell/)::
+(:pypi:`pospell`)::
 
     pip install pospell
 

.overrides/git_diff.rst

@@ -27,7 +27,7 @@ Primero debemos instalar brew. Si no lo tienes instalado puedes seguir el instru
 Una vez instalado brew, hay que instalar podiff, para ellos ejectar el siguiente comando:
 
 .. code-block:: bash
-   
+
    brew install podiff
 
 Luego abrir el archivo de configuración del respositorio local y escribir al final:
@@ -37,15 +37,15 @@ Luego abrir el archivo de configuración del respositorio local y escribir al fi
    [diff "podiff"]
    command = $(brew --prefix)/bin/podiff -D--minimal
 
-Luego, si no existiese el archivo `.gitatributes` en la carpeta dónde se encuentran los 
-archivos .po con los que se van a trabajar, crealo, y luego,  agregar la siguiente línea 
+Luego, si no existiese el archivo `.gitatributes` en la carpeta dónde se encuentran los
+archivos .po con los que se van a trabajar, crealo, y luego,  agregar la siguiente línea
 
 .. code-block:: bash
 
     *.po diff=podiff
 
-Para las distribuciones de Linux se pueden utilizar algunas herramientas, como por ejemplo podiff_ y
-potools_, que son compatibles con Python 2. Se puede utilizar `pip` para instalarlas.
+Para las distribuciones de Linux se pueden utilizar algunas herramientas, como por ejemplo :pypi:`podiff` y
+:pypi:`potools`, que son compatibles con Python 2. Se puede utilizar `pip` para instalarlas.
 
 .. code-block:: bash
 
@@ -54,5 +54,3 @@ potools_, que son compatibles con Python 2. Se puede utilizar `pip` para instala
     pip install potools
 
 .. _Brew: https://docs.brew.sh/Installation
-.. _podiff: https://pypi.org/project/podiff/
-.. _potools: https://pypi.org/project/potools/

.overrides/upgrade-python-version.rst

@@ -3,29 +3,25 @@
 How to update to a new Python version
 =====================================
 
-We are currently in branch 3.11, and we want to update the strings from 3.12.
+We are currently in branch 3.12, and we want to update the strings from 3.13.
 
-#. Make sure you are in a clean state of the branch 3.11
+#. Make sure you are in a clean state of the branch 3.12
 
-#. Create a new branch called ``3.12``
+#. Create a new branch called ``3.13``
 
 #. Initialize the submodules::
 
      git submodule init
      git submodule update
 
-#. Fetch the `latest commit of 3.12 branch <https://github.com/python/cpython/commit/0fb18b02c8ad56299d6a2910be0bab8ad601ef24>`_::
+#. Fetch the `latest release tag of 3.12  <https://github.com/python/cpython/releases/tag/v3.13.0>`_::
 
      cd cpython/
-     git fetch --depth 1 origin 0fb18b02c8ad56299d6a2910be0bab8ad601ef24
-
-   .. note:: you could also base the hash on the 'git tag' from the desired
-             version: ``git checkout tags/v3.12.0 -b 3.12`` considering that
-             ``3.12`` doesn't exist locally.
+     git fetch --depth 1 origin tags/v3.13.0
 
 #. Checkout that commit locally::
 
-     git checkout 0fb18b02c8ad56299d6a2910be0bab8ad601ef24
+     git checkout tags/v3.13.0 -b 3.13.0
 
 #. Update the branch on the ``Makefile`` and check the ``requirements.txt`` from
    ``./cpython/Doc`` directory, to see if upgrades on the modules like sphinx is
@@ -52,14 +48,17 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
 
    .. note::
 
+      You can also run `make build -j` to use more than 1 core (but keep in mind
+      this is not always faster).
+
       It may fail the build because there may be files
       that don't exist anymore in the new branch.
       If that's the case, just continue with the steps
       and verify the build later.
 
 #. Clean possible garbage (form previous builds)::
 
-     rm -rf _build ../python-docs-es-pot cpython/Doc/CONTRIBUTING.rst cpython/Doc/upgrade-python-version.rst reviewers-guide.rst
+     rm -rf _build cpython/python-docs-es-pot cpython/Doc/CONTRIBUTING.rst cpython/Doc/upgrade-python-version.rst reviewers-guide.rst
 
    .. note::
 
@@ -69,32 +68,16 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
 
 #. Create the .po files from the new source code. This will generate all the .po files for version 3.11::
 
-     SPHINX_GETTEXT=True sphinx-build -j auto -b gettext -d _build/doctrees . ../python-docs-es-pot
+     SPHINX_GETTEXT=True sphinx-build -j auto -b gettext -d _build/doctrees . cpython/python-docs-es-pot
 
    .. note::
 
-      In ``../python-docs-es-pot`` directory, we will have the new .pot files with new strings from 3.12 branch.
+      In ``cpython/python-docs-es-pot`` directory, we will have the new .pot files with new strings from 3.13 branch.
       All these strings will be *untranslated* at this point.
 
 #. 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/
-
-#. At this point, all the ``.po`` files will have a different comment on each translation phrase,
-   for example::
-
-     -#: ../python-docs-es/cpython/Doc/whatsnew/3.12.rst:3
-     +#: ../Doc/whatsnew/3.12.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.
+     sphinx-intl update --language es --pot-dir cpython/python-docs-es-pot --locale-dir cpython/locales/
 
 #. Pass ``powrap`` to make the column widths consistent::
 
@@ -116,13 +99,14 @@ We are currently in branch 3.11, and we want to update the strings from 3.12.
 **Once the process is completely and you are happy with the results,
 there are a few extra steps to finish the process**
 
-#. Upgrade GitHub Actions to use Python 3.12, by updating Python version to 3.12 in the ``.github/workflows/main.yml`` file.
+#. Upgrade GitHub Actions to use Python 3.13, by updating Python version to 3.13 in the ``.github/workflows/main.yml`` file.
 
-#. Update the *Read the Docs* project to use 3.12 in the build and also as default branch/version.
+#. Update the *Read the Docs* project to use 3.13 in the build and also as default branch/version.
 
 #. Commit all the newly created files locally.
 
-#. Create branch 3.12 in the repository in order to merge changes there.
+#. Create branch 3.13 in the repository in order to merge changes there.
 
-#. Inside the github project settings, set 3.12 branch as the default branch for the repository.
+#. Inside the github project settings, set 3.13 branch as the default branch for the repository.
 
+#. Create GitHub issues with [the script](../scripts/create_issue.py)