python
diff --git a/‎.github/workflows/tests.yml‎
Lines changed: 9 additions & 7 deletions b/‎.github/workflows/tests.yml‎
Lines changed: 9 additions & 7 deletions
diff --git a/‎Makefile‎
Lines changed: 1 addition & 1 deletion b/‎Makefile‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎about.po‎
Lines changed: 3 additions & 2 deletions b/‎about.po‎
Lines changed: 3 additions & 2 deletions
diff --git a/‎bugs.po‎
Lines changed: 52 additions & 38 deletions b/‎bugs.po‎
Lines changed: 52 additions & 38 deletions
diff --git a/‎c-api/allocation.po‎
Lines changed: 3 additions & 2 deletions b/‎c-api/allocation.po‎
Lines changed: 3 additions & 2 deletions
@@ -66,14 +66,18 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 30
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/cache@v2
+      - uses: actions/checkout@v3
+      - uses: actions/cache@v3
         with:
           path: '~/cpython/'
           key: '1'
-      - uses: actions/setup-python@v2
+      - uses: actions/cache@v3
         with:
-          python-version: '3.9'
+          path: ~/.cache/pip
+          key: '1'
+      - uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'
       - name: Clone cpython
         run: |
           if [ ! -d ~/cpython ]; then
@@ -88,9 +92,7 @@ jobs:
           git -C ~/cpython checkout $(grep ^CPYTHON_CURRENT_COMMIT Makefile| cut -d= -f2)
       - name: Prepare venv
         run: |
-          # If the venv exists but is broken, drop it (happens on Python upgrades):
-          # see https://github.com/actions/setup-python/issues/170
-          [ -d $HOME/cpython/Doc/venv/bin/ -a ! -e $HOME/cpython/Doc/venv/bin/python ] && rm -fr $HOME/cpython/Doc/venv
+          make -C $HOME/cpython/Doc clean-venv
           make -C $HOME/cpython/Doc venv
       - name: sphinx-build
         run: make -C $HOME/cpython/Doc SPHINXOPTS="-q -j4 -D locale_dirs=$HOME/locales -D language=fr -D gettext_compact=0" autobuild-dev-html
@@ -20,7 +20,7 @@
 # from which we generated our po files.  We use it here so when we
 # test build, we're building with the .rst files that generated our
 # .po files.
-CPYTHON_CURRENT_COMMIT := 3c2a1e7f4af3c5c54e04dfe9ac3a68d2351b00fb
+CPYTHON_CURRENT_COMMIT := b2db1c208066b67bdf57bf3799de50352fe63416
 LANGUAGE := fr
 BRANCH := 3.10
 
 
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-05-21 16:37+0200\n"
+"POT-Creation-Date: 2022-10-18 15:46+0200\n"
 "PO-Revision-Date: 2022-07-08 17:54+0200\n"
 "Last-Translator: Julien Palard <julien@palard.fr>\n"
 "Language-Team: FRENCH <traductions@lists.afpy.org>\n"
@@ -52,8 +52,9 @@ msgstr ""
 "et rédacteur de la plupart de son contenu ;"
 
 #: about.rst:24
+#, fuzzy
 msgid ""
-"the `Docutils <http://docutils.sourceforge.net/>`_ project for creating "
+"the `Docutils <https://docutils.sourceforge.io/>`_ project for creating "
 "reStructuredText and the Docutils suite;"
 msgstr ""
 "le projet `Docutils <http://docutils.sourceforge.net/>`_ pour avoir créé "
 
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-05-21 16:37+0200\n"
+"POT-Creation-Date: 2022-10-18 15:46+0200\n"
 "PO-Revision-Date: 2022-07-08 17:50+0200\n"
 "Last-Translator: Jean Abou Samra <jean@abou-samra.fr>\n"
 "Language-Team: FRENCH <traductions@lists.afpy.org>\n"
@@ -130,25 +130,28 @@ msgid "Using the Python issue tracker"
 msgstr "Utilisation du gestionnaire de tickets Python"
 
 #: bugs.rst:47
+#, fuzzy
 msgid ""
-"Bug reports for Python itself should be submitted via the Python Bug Tracker "
-"(https://bugs.python.org/).  The bug tracker offers a web form which allows "
-"pertinent information to be entered and submitted to the developers."
+"Issue reports for Python itself should be submitted via the GitHub issues "
+"tracker (https://github.com/python/cpython/issues). The GitHub issues "
+"tracker offers a web form which allows pertinent information to be entered "
+"and submitted to the developers."
 msgstr ""
 "Les rapports de bogues pour Python lui-même devraient être soumis via le "
 "l'outil de suivi des bogues (*Bug Tracker Python* — http://bugs.python."
 "org/). Le gestionnaire de tickets propose un formulaire Web permettant de "
 "saisir des informations pertinentes à soumettre aux développeurs."
 
-#: bugs.rst:51
+#: bugs.rst:52
+#, fuzzy
 msgid ""
 "The first step in filing a report is to determine whether the problem has "
 "already been reported.  The advantage in doing so, aside from saving the "
-"developers time, is that you learn what has been done to fix it; it may be "
+"developers' time, is that you learn what has been done to fix it; it may be "
 "that the problem has already been fixed for the next release, or additional "
 "information is needed (in which case you are welcome to provide it if you "
-"can!). To do this, search the bug database using the search box on the top "
-"of the page."
+"can!). To do this, search the tracker using the search box at the top of the "
+"page."
 msgstr ""
 "La première étape pour remplir un rapport est de déterminer si le problème a "
 "déjà été rapporté. L'avantage de cette approche, en plus d'économiser du "
@@ -158,13 +161,13 @@ msgstr ""
 "contribution est la bienvenue !). Pour ce faire, cherchez dans la base de "
 "données de bogues grâce à la boîte de recherche en haut de la page."
 
-#: bugs.rst:58
+#: bugs.rst:59
+#, fuzzy
 msgid ""
-"If the problem you're reporting is not already in the bug tracker, go back "
-"to the Python Bug Tracker and log in.  If you don't already have a tracker "
-"account, select the \"Register\" link or, if you use OpenID, one of the "
-"OpenID provider logos in the sidebar.  It is not possible to submit a bug "
-"report anonymously."
+"If the problem you're reporting is not already in the list, log in to "
+"GitHub. If you don't already have a GitHub account, create a new account "
+"using the \"Sign up\" link. It is not possible to submit a bug report "
+"anonymously."
 msgstr ""
 "Si le problème que vous soumettez n'est pas déjà dans l'outil de suivi des "
 "bogues, revenez au *Python Bug Tracker* et connectez-vous. Si vous n'avez "
@@ -173,29 +176,27 @@ msgstr ""
 "dans la barre latérale. Il n'est pas possible de soumettre un rapport de "
 "bogue de manière anonyme."
 
-#: bugs.rst:63
+#: bugs.rst:64
+#, fuzzy
 msgid ""
-"Being now logged in, you can submit a bug.  Select the \"Create New\" link "
-"in the sidebar to open the bug reporting form."
+"Being now logged in, you can submit an issue. Click on the \"New issue\" "
+"button in the top bar to report a new issue."
 msgstr ""
 "Une fois identifié, pour pouvez rapporter un bogue. Sélectionnez le lien "
 "*Create New* dans la barre latérale pour ouvrir un nouveau formulaire de "
 "rapport de bogue."
 
-#: bugs.rst:66
+#: bugs.rst:67
+msgid "The submission form has two fields, \"Title\" and \"Comment\"."
+msgstr ""
+
+#: bugs.rst:69
 msgid ""
-"The submission form has a number of fields.  For the \"Title\" field, enter "
-"a *very* short description of the problem; less than ten words is good.  In "
-"the \"Type\" field, select the type of your problem; also select the "
-"\"Component\" and \"Versions\" to which the bug relates."
+"For the \"Title\" field, enter a *very* short description of the problem; "
+"less than ten words is good."
 msgstr ""
-"Le formulaire de soumission a un certain nombre de champs. Pour le champ "
-"« Titre », saisissez une *très* courte description du problème ; moins de "
-"dix mots est approprié. Dans le champ « Type », sélectionnez le type de "
-"problème ; sélectionnez aussi « Composant » et « Versions » en rapport avec "
-"le bogue."
 
-#: bugs.rst:71
+#: bugs.rst:72
 msgid ""
 "In the \"Comment\" field, describe the problem in detail, including what you "
 "expected to happen and what did happen.  Be sure to include whether any "
@@ -208,25 +209,26 @@ msgstr ""
 "plateforme matérielle et logicielle vous utilisiez (en incluant les "
 "informations de versions)."
 
-#: bugs.rst:76
+#: bugs.rst:77
+#, fuzzy
 msgid ""
-"Each bug report will be assigned to a developer who will determine what "
-"needs to be done to correct the problem.  You will receive an update each "
-"time action is taken on the bug."
+"Each issue report will be reviewed by a developer who will determine what "
+"needs to be done to correct the problem. You will receive an update each "
+"time an action is taken on the issue."
 msgstr ""
 "Chaque bogue sera attribué à un développeur qui déterminera ce qui est "
 "nécessaire d'entreprendre pour corriger le problème. Vous recevrez une "
 "notification à chaque action effectuée sur le bogue."
 
-#: bugs.rst:85
+#: bugs.rst:86
 msgid ""
 "`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
 "~sgtatham/bugs.html>`_"
 msgstr ""
 "`Comment signaler des bogues de manière efficace <https://www.chiark."
 "greenend.org.uk/~sgtatham/bugs.html>`_ (en anglais)"
 
-#: bugs.rst:84
+#: bugs.rst:85
 msgid ""
 "Article which goes into some detail about how to create a useful bug report. "
 "This describes what kind of information is useful and why it is useful."
@@ -235,27 +237,27 @@ msgstr ""
 "bogue utile. Il décrit quel genre d'information est utile et pourquoi elle "
 "est utile."
 
-#: bugs.rst:88
+#: bugs.rst:89
 msgid ""
 "`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
 "writing.html>`_"
 msgstr ""
 "`Guide pour la rédaction de rapports de bogues <https://bugzilla.mozilla.org/"
 "page.cgi?id=bug-writing.html>`_"
 
-#: bugs.rst:88
+#: bugs.rst:89
 msgid ""
 "Information about writing a good bug report.  Some of this is specific to "
 "the Mozilla project, but describes general good practices."
 msgstr ""
 "Conseils pour écrire un bon rapport de bogue. Certains sont spécifiques au "
 "projet Mozilla mais présentent des bonnes pratiques générales."
 
-#: bugs.rst:94
+#: bugs.rst:95
 msgid "Getting started contributing to Python yourself"
 msgstr "Commencer à contribuer à Python vous-même"
 
-#: bugs.rst:96
+#: bugs.rst:97
 msgid ""
 "Beyond just reporting bugs that you find, you are also welcome to submit "
 "patches to fix them.  You can find more information on how to get started "
@@ -269,3 +271,15 @@ msgstr ""
 "Developer's Guide`_. Si vous avez des questions, le `core-mentorship mailing "
 "list`_ est un endroit amical pour obtenir des réponses à toutes les "
 "questions à propos du processus de corrections de bugs dans Python."
+
+#~ msgid ""
+#~ "The submission form has a number of fields.  For the \"Title\" field, "
+#~ "enter a *very* short description of the problem; less than ten words is "
+#~ "good.  In the \"Type\" field, select the type of your problem; also "
+#~ "select the \"Component\" and \"Versions\" to which the bug relates."
+#~ msgstr ""
+#~ "Le formulaire de soumission a un certain nombre de champs. Pour le champ "
+#~ "« Titre », saisissez une *très* courte description du problème ; moins de "
+#~ "dix mots est approprié. Dans le champ « Type », sélectionnez le type de "
+#~ "problème ; sélectionnez aussi « Composant » et « Versions » en rapport "
+#~ "avec le bogue."
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-08-24 09:01+0200\n"
+"POT-Creation-Date: 2022-10-18 15:46+0200\n"
 "PO-Revision-Date: 2018-10-20 21:16+0200\n"
 "Last-Translator: Julien Palard <julien@palard.fr>\n"
 "Language-Team: FRENCH <traductions@lists.afpy.org>\n"
@@ -20,8 +20,9 @@ msgid "Allocating Objects on the Heap"
 msgstr "Allouer des objets dans le tas"
 
 #: c-api/allocation.rst:17
+#, fuzzy
 msgid ""
-"Initialize a newly-allocated object *op* with its type and initial "
+"Initialize a newly allocated object *op* with its type and initial "
 "reference.  Returns the initialized object.  If *type* indicates that the "
 "object participates in the cyclic garbage detector, it is added to the "
 "detector's set of observed objects. Other fields of the object are not "