makefile + readme updates

acuccie3 · acuccie3 · commit d1f64bbc5460 · 2024-05-30T10:28:35.000+02:00
diff --git a/Makefile b/Makefile
@@ -21,7 +21,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 := 7a9534f595ccd9f2bdea5ceeecb837a82e44c620
+CPYTHON_CURRENT_COMMIT := 083bf3ad1795604ee833d1595f2a536b9cd57419
 
 CPYTHON_PATH := ../cpython/
 
@@ -35,7 +35,7 @@ EXCLUDED := \
 	install/ \
 	library/ 
 
-SPHINXERRORHANDLING = 
+SPHINXERRORHANDLING = # -W
 
 # Internal variables
 
diff --git a/README.rst b/README.rst
@@ -1,7 +1,7 @@
 Translation of the Python Documentation — it
 ============================================
 
-.. image:: https://travis-ci.org/python/python-docs-it.svg?branch=3.7
+.. image:: https://travis-ci.org/python/python-docs-it.svg?branch=3.13
   :target: https://travis-ci.org/python/python-docs-it
 
 
@@ -10,7 +10,7 @@ Documentation Contribution Agreement
 
 NOTE REGARDING THE LICENSE FOR TRANSLATIONS: Python's documentation is
 maintained using a global network of volunteers. By posting this
-project on Transifex, Github, and other public places, and inviting
+project on Github, and other public places, and inviting
 you to participate, we are proposing an agreement that you will
 provide your improvements to Python's documentation or the translation
 of Python's documentation for the PSF's use under the CC0 license
@@ -37,7 +37,6 @@ 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>`_
 
 
@@ -64,8 +63,15 @@ Step by step:
 
 .. code-block:: bash
 
+    # Create a working directory
+    mkdir cpython_projects
+    cd cpython_projects
+
+    # Git clone cpython code
+    git clone git@github.com:python/cpython.git
+
     # Git clone your github fork using ssh:
-    git clone git@github.com:alessandrocucci/python-docs-it.git
+    git clone git@github.com:yourusername/python-docs-it.git
 
     # Go to the cloned directory:
     cd python-docs-it/
@@ -75,7 +81,7 @@ Step by step:
 
 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.
+is python 3.13, we don't want to translate directly on the python 3.12 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>`.
 
@@ -84,10 +90,10 @@ Now you're ready to start a work session, each time you'll start a new task, sta
 .. 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
+    # upstream/3.13 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
+    git checkout -b glossary upstream/3.13
 
     # You can now work on the file, typically using poedit,
     poedit directory/file.po
