deploy: pypackaging-native/pypackaging-native@767052f

Author: github-actions[bot]

key-issues/pypi_metadata_handling/index.html

@@ -1194,15 +1194,14 @@ <h3 id="metadata-contained-within-artifacts">Metadata contained within artifacts
 for example the <code>METADATA</code> or <code>RECORD</code> files, the current process is slow and
 bandwidth-intensive.</p>
 <p>The solution seems obvious: make metadata separately accessible from wheels.
-Luckily, the solution for this is currently in progress:</p>
+Luckily, the solution for this is now available:</p>
 <div class="admonition note">
-<p class="admonition-title">PEP 568 - Serve Distribution Metadata in the Simple Repository API</p>
-<p><a href="https://peps.python.org/pep-0658/">PEP 568</a> (accepted) proposes to make the
+<p class="admonition-title">PEP 658 - Serve Distribution Metadata in the Simple Repository API</p>
+<p><a href="https://peps.python.org/pep-0658/">PEP 658</a> (accepted) proposed to make the
 metadata file in the <code>.dist-info</code> directory of a wheel separately available.
-This should solve the problems identified in this section. Support is
-<a href="https://github.com/pypa/pip/pull/11111">already implemented in <code>pip</code></a>.
-Implementation in PyPI is still pending, see
-<a href="https://github.com/pypi/warehouse/issues/8254">warehouse#8254</a>.</p>
+This solves the problems identified in this section. Support is
+<a href="https://github.com/pypa/pip/pull/11111">implemented in <code>pip</code></a>, and
+<a href="https://github.com/pypi/warehouse/issues/8254">PyPI</a>.</p>
 </div>
 <p>There are also issues around packages who don't yet use static metadata in
 <code>pyproject.toml</code>, and reliable metadata for sdists being only relatively
@@ -1239,7 +1238,7 @@ <h2 id="potential-solutions-or-mitigations">Potential solutions or mitigations</
   bounds the way they currently do, as discussed in
   <a href="https://discuss.python.org/t/requires-python-upper-limits/12663">this thread</a>.
   Pip also needs to continue reducing the amount of excessive backtracking, and
-  use the separate metadata available soon with PEP 568 to reduce the impact of
+  use the separate metadata available with PEP 658 to reduce the impact of
   that backtracking. See
   <a href="https://pip.pypa.io/en/latest/topics/dependency-resolution/#possible-ways-to-reduce-backtracking">Possible ways to reduce backtracking</a>
   in the Pip docs for current mitigation options available to users.</li>
@@ -1285,7 +1284,7 @@ <h2 id="potential-solutions-or-mitigations">Potential solutions or mitigations</
     <span class="md-icon" title="Last update">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1-2.1-2M12.5 7v5.2l4 2.4-1 1L11 13V7h1.5M11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2v1.8Z"/></svg>
     </span>
-    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">December 26, 2022</span>
+    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">June 26, 2024</span>
   </span>