Remove emscripten_3_1_58 tag

Author: hoodmane

peps/pep-0776.rst

@@ -652,26 +652,21 @@ packages like aiohttp, Requests, Pydantic, cryptography, and orjson.
 About 60 packages are also testing against Pyodide in their CI, including NumPy,
 pandas, awkward-cpp, scikit-image, statsmodels, PyArrow, Hypothesis, and PyO3.
 
-Emscripten Wheel Tags
-~~~~~~~~~~~~~~~~~~~~~
-
-Emscripten wheels will use as the platform tag either
-``emscripten_<version>_wasm32`` or ``pyodide_<abi>_wasm32``. For example:
+Pyodide Wheel Tags
+~~~~~~~~~~~~~~~~~~
 
-* ``emscripten_3_1_58_wasm32``
-* ``pyodide_2025_0_wasm32``
+Pyodide wheels will use ``pyodide_<abi>_wasm32`` as the platform tag. For
+example, ``pyodide_2025_0_wasm32``.
 
-The first triple is ambiguous, since even with Emscripten 3.1.58 it is possible
-to link dynamic libraries that require a large number of distinct ABIs,
-depending on linker and compiler options. It is our intent that the
-``pyodide_2025_0`` specifies the particular ABI. Thus, the relationship between
-``pyodide_<abi>`` and ``emscripten_<version>`` is intended to be the same as the
-relationship between ``manylinux<version>`` and ``linux``.
+With a fixed version of Emscripten, it is possible to link dynamic libraries
+that require a large number of distinct ABIs, depending on ABI-sensitive linker
+options and what versions of what static libraries are linked. It is our intent
+that the ``pyodide_2025_0`` specifies the particular ABI that will work with the
+Pyodide CPython runtime.
 
 For example, wheels with the following tags are compatible with Python 3.13
 Pyodide:
 
-- ``cp13-cp13-emscripten_3_1_58_wasm32``
 - ``cp13-cp13-pyodide_2025_0_wasm32``
 - ``abi3-cp10-pyodide_2025_0_wasm32``