amend deprecation notes

Author: picnixz

Doc/deprecations/pending-removal-in-3.17.rst

@@ -1,17 +1,6 @@
 Pending removal in Python 3.17
 ------------------------------
 
-* :mod:`hashlib`:
-
-  - Supporting the undocumented ``string`` keyword parameter in :func:`~hashlib.new`
-    and hash function constructors such as :func:`~hashlib.md5` is deprecated.
-    Use the ``data`` keyword parameter instead, or simply pass the data to hash
-    as a positional argument.
-
-    Before Python 3.13, the ``string`` keyword parameter was not correctly
-    supported depending on the backend implementation of hash functions, and
-    users should prefer passing the data to hash as a positional argument.
-
 * :mod:`typing`:
 
   - Before Python 3.14, old-style unions were implemented using the private class

Doc/deprecations/pending-removal-in-3.19.rst

@@ -6,3 +6,19 @@ Pending removal in Python 3.19
   * Implicitly switching to the MSVC-compatible struct layout by setting
     :attr:`~ctypes.Structure._pack_` but not :attr:`~ctypes.Structure._layout_`
     on non-Windows platforms.
+
+* :mod:`hashlib`:
+
+  - In hash function constructors such as :func:`~hashlib.new` or the
+    direct hash-named constructors such as :func:`~hashlib.md5` and
+    :func:`~hashlib.sha256`, their optional initial data parameter could
+    also be passed a keyword argument named ``data=`` or ``string=`` in
+    various :mod:`!hashlib` implementations.
+
+    Support for the ``string`` keyword argument name is now deprecated
+    and slated for removal in Python 3.19.
+
+    Before Python 3.13, the ``string`` keyword parameter was not correctly
+    supported depending on the backend implementation of hash functions.
+    Prefer passing the initial data as a positional argument for maximum
+    backwards compatibility.

Doc/whatsnew/3.15.rst

@@ -132,11 +132,16 @@ Deprecated
 hashlib
 -------
 
-* Supporting the undocumented ``string`` keyword parameter in
-  :func:`~hashlib.new` and hash function constructors such as
-  :func:`~hashlib.md5` is deprecated and slated for removal in Python 3.17.
-  Use the ``data`` keyword parameter instead, or simply pass the data to hash
-  as a positional argument.
+* In hash function constructors such as :func:`~hashlib.new` or the
+  direct hash-named constructors such as :func:`~hashlib.md5` and
+  :func:`~hashlib.sha256`, their optional initial data parameter could
+  also be passed a keyword argument named ``data=`` or ``string=`` in
+  various :mod:`hashlib` implementations.
+
+  Support for the ``string`` keyword argument name is now deprecated and
+  is slated for removal in Python 3.19. Prefer passing the initial data as
+  a positional argument for maximum backwards compatibility.
+
   (Contributed by Bénédikt Tran in :gh:`134978`.)
 
 

Misc/NEWS.d/next/Library/2025-05-31-15-49-46.gh-issue-134978.mXXuvW.rst

@@ -1,5 +1,7 @@
-Supporting the undocumented ``string`` keyword parameter in :func:`hashlib.new`
-and hash function constructors such as :func:`hashlib.md5` is deprecated and
-slated for removal in Python 3.17. Use the ``data`` keyword parameter instead,
-or simply pass the data to hash as a positional argument.
+:mod:`hashlib`: Supporting the ``string`` keyword parameter in hash function
+constructors such as :func:`~hashlib.new` or the direct hash-named constructors
+such as :func:`~hashlib.md5` and :func:`~hashlib.sha256` is now deprecated and
+slated for removal in Python 3.19.
+Prefer passing the initial data as a positional argument for maximum backwards
+compatibility.
 Patch by Bénédikt Tran.