python
diff --git a/‎.gitignore
-1 b/‎.gitignore
-1
diff --git a/‎Makefile
-85 b/‎Makefile
-85
diff --git a/‎README.rst
+3-281 b/‎README.rst
+3-281
diff --git a/‎TRANSLATORS
-1 b/‎TRANSLATORS
-1
@@ -28,285 +28,7 @@ You signify acceptance of this agreement by submitting your work to
 the PSF for inclusion in the documentation.
 
 
-Contributing to the Translation
--------------------------------
+python-docs-it source code
+--------------------------
 
-How to Contribute
-~~~~~~~~~~~~~~~~~
-
-You can contribute using:
-
-- Github
-- `transifex <https://www.transifex.com/python-doc/public/>`_
-- Or just by opening `an issue on github <https://github.com/python/python-docs-it/issues>`_
-
-
-Contributing using Github
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Prerequisites:
-
-- A `github account <https://github.com/join>`_.
-- ``git`` `installed <https://help.github.com/articles/set-up-git/>`_ (for windows, see
-  https://gitforwindows.org/).
-- A ``.po`` file editor (Use `poedit <https://poedit.net/>`_
-  if you don't already have one).
-
-
-Let's start:
-
-You'll need to fork the `python-docs-it
-<https://github.com/python/python-docs-it>`_ clicking its ``Fork``
-button. This creates a copy of the whole project on your github
-account: a place where you have the rights to do modifications.
-
-Step by step:
-
-.. code-block:: bash
-
-    # Git clone your github fork using ssh:
-    git clone git@github.com:alessandrocucci/python-docs-it.git
-
-    # Go to the cloned directory:
-    cd python-docs-it/
-
-    # Add the upstream (the public repository) using HTTPS (won't ask for password):
-    git remote add upstream https://github.com/python/python-docs-it.git
-
-All the translations must be made on the latest release.
-We never translate on an oldest version, by example, the latest python release
-is python 3.7, we don't want to translate directly on the python 3.5 release.
-If needed translations would be backported on the oldest versions by the
-`documentation team <https://www.python.org/dev/peps/pep-8015/#documentation-team>`.
-
-Now you're ready to start a work session, each time you'll start a new task, start here:
-
-.. code-block:: bash
-
-    # To work, we'll need a branch, based on an up-to-date (freshly fetched)
-    # upstream/3.7 branch, let's say we'll work on glossary so we name
-    # the branch "glossary":
-    git fetch upstream
-    git checkout -b glossary upstream/3.7
-
-    # You can now work on the file, typically using poedit,
-    poedit directory/file.po
-
-    # When everything is clear (syntax errors from Sphinx, html rendering,
-    # semantics, typography),
-    # you can commit your work with a nice explicit message:
-    git commit -a -m "Working on glossary."
-
-    # Then push your modifications to your github clone,
-    # as they are ephemeral branches, let's not configure git to track them all,
-    # "origin HEAD" is a "special" syntax to say "Push on origin,
-    # on a branch with the same name as the local one",
-    # it's nice as it's exactly what we want:
-    git push origin HEAD
-
-    # The previous command will print you a link to open a PR on github.
-    # If you missed it, just go to
-    # https://github.com/python/python-docs-it and a nice "Compare & pull request"
-    # button should appear after a few seconds telling you can ask for a pull request.
-
-    # Now someone is reviewing your modifications, and you'll want to fix their
-    # findings, get back to your branch
-    # (in case you started something else on another branch):
-    git checkout glossary
-    # Fix the issues, then commit again:
-    git commit -a -m "glossary: small fixes."
-    git push origin HEAD
-
-
-You may have noted that this looks like a triangle, with a missing segment:
-
-- You're fetching from upstream (public common repo on github)
-- You're pushing to origin (your clone on github)
-
-So yes it's the work of someone to add the last segment, from your
-origin to the public upstream, to "close the loop", that's the role of
-the people who merges pull requests after proofreading them.
-
-You may also have noted you never ever commit on a version branch
-(``3.6``, ``3.7``, ...), only pull from them, consider them read-only
-you'll avoid problems.
-
-
-What to translate
-~~~~~~~~~~~~~~~~~
-
-You can start with easy tasks like reviewing fuzzy entries to help
-keeping the documentation up to date (find them using ``make fuzzy``).
-
-You can also proofread already translated entries, and finally
-translate untranslated ones (find them using ``make todo``)..
-
-- Do not translate content of ``:ref:...`` and ``:term:...``
-- Put english words, if you have to use them, in *italics* (surrounded
-  by stars).
-- If you translate a link title, please translate the link too
-  (typically if it's Wikipedia and the article has a translation). If
-  no translation of the target exists, do not translate the
-  title.
-
-
-Where to get help
-~~~~~~~~~~~~~~~~~
-
-The coordinator for this translation is `acucci <https://www.alessandrocucci.it/>`_.
-
-Feel free to ask your questions on the ``#python-it`` channel on `freenode
-<https://webchat.freenode.net/>`_ (does not require registration)
-
-
-Translation Resources
----------------------
-
-- IRC channel `#python-it <http://irc.lc/freenode/python-it>`_ on freenode.
-- The `doc-sig mailing list
-  <https://mail.python.org/mailman/listinfo/doc-sig>`_.
-- `deepl.com/translator <https://www.deepl.com>`_
-
-
-Glossary
---------
-
-For consistency in our translations, here are some propositions and
-reminders for frequent terms you'll have to translate, don't hesitate
-to open an issue if you disagree.
-
-To easily find how a term is already translated in our documentation,
-you may use
-`find_in_po.py <https://gist.github.com/JulienPalard/c430ac23446da2081060ab17bf006ac1>`_.
-
-========================== ===========================================
-Term                       Proposed Translation
-========================== ===========================================
--like                      di tipo
-abstract data type         tipo dato astratto
-argument                   argomento
-backslash                  barra rovescia, *backslash*
-bound                      legato a
-bug                        errore, *bug*
-built-in                   integrato   
-call stack                 pila
-debugging                  *debugging*
-deep copy                  copia profonda, copia ricorsiva
-double quote               doppi apici
-e.g.                       per esempio
-garbage collector          *garbage collector*
-identifier                 identificatore
-immutable                  immutabile
-installer                  *installer*
-interpreter                interprete
-library                    libreria
-list comprehension         *list comprehension*
-little-endian, big-endian  formato *little-endian*, formato *big-endian*
-mutable                    mutevole
-namespace                  spazio dei nomi
-parameter                  parametro
-prompt                     *prompt*
-raise                      sollevare
-regular expression         espressione regolare
-return                     ritorno 
-simple quote               singoli apici
-socket                     *socket*
-statement                  dichiarazione
-subprocess                 sottoprocesso
-thread                     *thread*
-underscore                 *underscore*
-expression                 espressione
-========================== ===========================================
-
-
-Simplify git diffs
-------------------
-
-Git diffs are often crowded with useless line number changes, like:
-
-.. code-block:: diff
-
-    -#: ../Doc/library/signal.rst:406
-    +#: ../Doc/library/signal.rst:408
-
-To tell git they are not usefull information, you can do the following
-after ensuring ``~/.local/bin/`` is in your ``PATH``.
-
-.. code-block:: bash
-
-    cat <<EOF > ~/.local/bin/podiff
-    #!/bin/sh
-    grep -v '^#:' "\$1"
-    EOF
-
-    chmod a+x ~/.local/bin/podiff
-
-    git config diff.podiff.textconv podiff
-
-
-Maintenance
------------
-
-All those snippets are to run from the root of a ``python-docs-it``
-clone, and some expect to find an up-to-date CPython clone near to it,
-like:
-
-.. code-block:: bash
-
-  ~/
-  ├── python-docs-it/
-  └── cpython/
-
-To clone CPython you may use:
-
-.. code-block:: bash
-
-  git clone --depth 1 --no-single-branch https://github.com/python/cpython.git
-
-This avoids to download the whole history (not usefull to build
-documentation) but still fetches all branches.
-
-
-Merge pot files from CPython
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. code-block:: bash
-
-  make merge
-
-
-Find fuzzy strings
-~~~~~~~~~~~~~~~~~~
-
-.. code-block:: bash
-
-  make fuzzy
-
-
-Run a test build locally
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. code-block:: bash
-
-  make
-
-
-Synchronize translation with Transifex
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You'll need the ``transifex-client`` and ``powrap``
-from Pypi.
-
-You'll need to configure ``tx`` via ``tx init`` if not already done.
-
-.. code-block:: bash
-
-   pomerge --from-files **/*.po
-   tx pull -f
-   pomerge --to-files **/*.po
-   pomerge --from-files **/*.po
-   git checkout -- .
-   pomerge --to-files **/*.po
-   powrap --modified
-   git commit -m "tx pull"
-   tx push -t -f
+You can check the latest sources switching to the `3.13` branch.