Merge branch 'main' into windows-certificate-revocation-criteria

Author: sethmlarson

core-team/experts.rst

@@ -251,6 +251,7 @@ xmlrpc
 zipapp                pfmoore
 zipfile               alanmcintyre^, serhiy-storchaka, Yhg1s, gpshead
 zipimport             Yhg1s*
+zoneinfo              pganssle
 ====================  =============================================
 
 

documentation/translations/coordinating.rst

@@ -12,8 +12,7 @@ Communication/help channels
 ===========================
 
 Discussions about translations occur on the Python Docs Discord
-`#translations channel <https://discord.gg/h3qDwgyzga>`_, `translation
-mailing list <translation_ml_>`_, and the
+`#translations channel <https://discord.gg/h3qDwgyzga>`_ and the
 `translations category <trans_disc_>`_ of the Python Discourse.
 
 For administrative issues, ping ``@python/editorial-board``.
@@ -175,9 +174,7 @@ Translating Sphinx
 Some messages that appear in the docs must be translated in the
 `Sphinx project <https://www.sphinx-doc.org/en/master/internals/contributing.html#translations>`__
 (`sphinx-doc on Transifex <https://app.transifex.com/sphinx-doc/>`__) or in
-the `python-docs-theme <https://github.com/python/python-docs-theme>`_
-(currently this is not possible; see this
-`issue <https://github.com/python/python-docs-theme/issues/194>`__).
+the :ref:`Python Docs Sphinx Theme <python-docs-theme-i18n>`.
 Coordinators should direct some translators there, so that the documentation
 is fully translated.
 
@@ -226,7 +223,8 @@ How is a coordination team chosen?
 Each translation team will decide on the number of coordinators.
 We recommend two or three coordinators, though you may begin with one.
 
--  Coordinator requests are to be public on the `translation mailing list <translation_ml_>`_.
+-  Coordinator requests are to be public in the `translations category of the
+   Python Discourse <trans_disc_>`_.
 -  If the given language has a native core team member, they have input
    on the coordinator request.
 -  Anyone who wants to become coordinator for their native language and shows
@@ -235,8 +233,8 @@ We recommend two or three coordinators, though you may begin with one.
 -  We expect the local community to self-organize coordinators and contributors.
    If you have questions, please ask on the mailing list or Discourse.
 -  If a coordinator becomes inactive or unreachable for a long
-   period of time, someone else can ask to be added as a primary coordinator on
-   the `translation mailing list <translation_ml_>`_.
+   period of time, someone else can ask to be added as a primary coordinator in
+   the `translations category of the Python Discourse <trans_disc_>`_.
    As a community resource, we aim to keep translations up to date with active
    contributors, including coordinators.
 
@@ -296,6 +294,5 @@ for updates.
 
 
 .. _EB: https://python.github.io/editorial-board/
-.. _translation_ml: https://mail.python.org/mailman3/lists/translation.python.org/
 .. _trans_disc: https://discuss.python.org/c/documentation/translations/
 .. _docsbuild-scripts: https://github.com/python/docsbuild-scripts

documentation/translations/translating.rst

@@ -125,9 +125,8 @@ If there is already a repository for your language team (there may be links to
 Telegrams/Discords in the ``README``), join and introduce
 yourself. Your fellow translators will be more than happy to help!
 General discussions about translations occur on the Python Docs Discord
-`#translations channel <https://discord.gg/h3qDwgyzga>`_, `translation
-mailing list <translation_ml_>`_, and the `translations category <discourse_>`_
-of the Python Discourse.
+`#translations channel <https://discord.gg/h3qDwgyzga>`_ and the
+`translations category <discourse_>`_ of the Python Discourse.
 
 .. _translation-style-guide:
 
@@ -209,7 +208,7 @@ Some general guidelines for deciding on a translation:
 Dialects
 --------
 
-Some translation receive contributions from people of several different dialects,
+Some translations receive contributions from people of several different dialects,
 understandably the language will differ. It is recommended however that
 translators try to keep files and sections consistent.
 
@@ -234,14 +233,16 @@ is provided below:
            print(kw, ":", keywords[kw])
 
 
+.. _transifex-use:
+
 Transifex
 =========
 
 .. important::
 
    There are many translations in the `python-doc organization on Transifex <tx_>`_,
    some of which, however, are not used or do not have a coordination team.
-   Confirm this is not the case before you begin translating.
+   Confirm that a coordination team exists before you begin translating.
 
 Several language projects use Transifex as their translation interface.
 Translations on Transifex are carried out via a web interface, similar to Weblate.
@@ -258,6 +259,9 @@ through the following resources from the Transifex documentation:
 - `Starting with the basics <https://help.transifex.com/en/collections/3441044-starting-with-the-basics>`__:
    A group of documents with basic information.
 
+Within the organization, a project for translating the
+:github:`Python Docs Sphinx Theme <python/python-docs-theme>` can also be
+found.
 For further information about Transifex see our `documentation <https://python-docs-transifex-automation.readthedocs.io/>`_.
 
 
@@ -287,6 +291,45 @@ be the latest non-alpha branch), the translations should then be propagated by
 your languages coordination team.
 
 
+.. _python-docs-theme-i18n:
+
+How do I translate the Python Docs Sphinx Theme?
+------------------------------------------------
+
+The Sphinx theme for the Python documentation supports localization.
+
+You can translate either on
+`Transifex <https://explore.transifex.com/python-doc/python-docs-theme/>`_
+(see :ref:`translating on Transifex <transifex-use>` for more information)
+or locally by following the steps outlined below.
+
+To translate locally, clone the :github:`Python Docs Sphinx Theme repository <python/python-docs-theme>` and run the following
+commands to generate the PO files. Replace ``LANG`` with the same language code
+that is used for the docs translation:
+
+.. code-block:: bash
+
+    python babel_runner.py extract
+    python babel_runner.py init -l LANG
+
+The file can then be found at:
+
+.. code-block:: text
+
+    python-docs-theme/locale/LANG/LC_MESSAGES/python-docs-theme.po
+
+After translating, submit your PO file via a pull request to the
+:github:`repository <python/python-docs-theme>`.
+See our :ref:`git-boot-camp` for more information about using Git.
+
+To update an existing translation after source changes, run:
+
+.. code-block:: bash
+
+    python babel_runner.py update  # To update source for all languages
+    python babel_runner.py update -l LANG  # To update source just for LANG
+
+
 The coordination team for my language is inactive, what do I do?
 ----------------------------------------------------------------
 
@@ -295,6 +338,5 @@ If you would like to coordinate, open a pull request in the
 at the top of this page, and ping ``@python/editorial-board``.
 
 
-.. _translation_ml: https://mail.python.org/mailman3/lists/translation.python.org/
 .. _discourse: https://discuss.python.org/c/documentation/translations/
 .. _tx: https://explore.transifex.com/python-doc/python-newest/

getting-started/setup-building.rst

@@ -511,13 +511,26 @@ The simplest way to install the Emscripten compiler is:
 
     # Install Emscripten
     git clone https://github.com/emscripten-core/emsdk
-    ./emsdk/emsdk install 4.0.5
-    ./emsdk/emsdk activate 4.0.5
+    ./emsdk/emsdk install 4.0.12
+    ./emsdk/emsdk activate 4.0.12
     source ./emsdk/emsdk_env.sh
 
-Updating the Emscripten compiler version often causes breakages. For the best
-compatibility, use the Emscripten version suggested in the cpython repository in
-``Tools/wasm/README.md``.
+Updating the Emscripten compiler version can cause breakages. For the best
+compatibility, use the appropriate Emscripten version based on the version of
+CPython you're building:
+
+* For building CPython 3.14, use ``emsdk`` version ``4.0.12``.
+* For building the main branch of the CPython repository, you may wish to use
+  ``latest`` instead of a specific version.
+
+It is possible (but not necessary) to enable ``ccache`` for Emscripten builds
+by setting the ``EM_COMPILER_WRAPPER`` environment, but this step will only
+take effect if it is done **after** ``emsdk_env.sh`` is sourced (otherwise, the
+sourced script removes the environment variable):
+
+.. code-block:: sh
+
+   export EM_COMPILER_WRAPPER=ccache
 
 Building for Emscripten requires doing a cross-build where you have a *build*
 Python to help produce an Emscripten build of CPython. This means you build
@@ -526,8 +539,8 @@ another that's the build you ultimately care about (that is, the build Python is
 not meant for use by you directly, only the build system).
 
 The easiest way to get a debug build of CPython for Emscripten is to use the
-``Tools/wasm/emscripten build`` command (which should be run with a recent
-version of Python you have installed on your machine):
+``Tools/wasm/emscripten build`` command, which should be run with a recent
+version of Python (3.13 or newer) already installed on your machine:
 
 .. code-block:: shell
 
@@ -545,6 +558,7 @@ is a convenience wrapper around the following commands:
    python Tools/wasm/emscripten configure-build-python --quiet -- --config-cache --with-pydebug
    python Tools/wasm/emscripten make-build-python --quiet
    python Tools/wasm/emscripten make-libffi --quiet
+   python Tools/wasm/emscripten make-mpdec --quiet
    python Tools/wasm/emscripten configure-host --quiet -- --config-cache
    python Tools/wasm/emscripten make-host --quiet
 
@@ -572,6 +586,9 @@ used in ``python.sh``:
 
    make -C cross-build/wasm32-emscripten/build/python/ test
 
+Additional instructions for running the resulting builds (through Node.js and/or
+through web browsers) are available in the CPython repository at
+:cpy-file:`Tools/wasm/README.md`.
 
 .. _Emscripten: https://emscripten.org/
 .. _WebAssembly: https://webassembly.org
@@ -797,7 +814,8 @@ some of CPython's modules (for example, ``zlib``).
       $ sudo apt-get install build-essential gdb lcov pkg-config \
             libbz2-dev libffi-dev libgdbm-dev libgdbm-compat-dev liblzma-dev \
             libncurses5-dev libreadline6-dev libsqlite3-dev libssl-dev \
-            lzma lzma-dev tk-dev uuid-dev zlib1g-dev libmpdec-dev libzstd-dev
+            lzma lzma-dev tk-dev uuid-dev zlib1g-dev libmpdec-dev libzstd-dev \
+            inetutils-inetd
 
    Note that Debian 12 and Ubuntu 24.04 do not have the ``libmpdec-dev``
    package.  You can safely remove it from the install list above and the