From 90ed88987c9b06412eec48c77316ee009c64bbe6 Mon Sep 17 00:00:00 2001 From: Emma Harper Smith Date: Mon, 7 Apr 2025 18:11:10 -0700 Subject: [PATCH 1/3] Add link to RFC 8478 --- peps/pep-0784.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/peps/pep-0784.rst b/peps/pep-0784.rst index ac8c43e7d3c..cd07abe73ac 100644 --- a/peps/pep-0784.rst +++ b/peps/pep-0784.rst @@ -44,7 +44,8 @@ significantly faster than LZMA. Zstandard has seen `widespread adoption`_ in many different areas of computing. The numerous hardware implementations demonstrate long-term commitment to Zstandard and an expectation that Zstandard will stay the *de facto* choice for -compression for years to come. Zstandard compression is also implemented in +compression for years to come. This is further evidenced by Zstandard's IETF +standardization in :rfc:`8478`. Zstandard compression is also implemented in both the ZFS_ and Btrfs_ filesystems. Zstandard's highly efficient compression has supplanted other modern From 7b83a5320db604c3f50b67bda62a81947d930213 Mon Sep 17 00:00:00 2001 From: Emma Harper Smith Date: Mon, 7 Apr 2025 18:22:13 -0700 Subject: [PATCH 2/3] Add updated timeline verbiage --- peps/pep-0784.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/peps/pep-0784.rst b/peps/pep-0784.rst index cd07abe73ac..e65db84d9ac 100644 --- a/peps/pep-0784.rst +++ b/peps/pep-0784.rst @@ -231,12 +231,14 @@ Compression module migration timeline Existing modules will emit a ``DeprecationWarning`` in the Python release following the last Python without the ``compression`` module leaving support. For example, if the ``compression`` namespace is introduced in 3.14, -then the ``DeprecationWarnings`` would be emitted in 3.19, the next release -after 3.13 reaches end of life. Following the standard deprecation timeline -specified in :pep:`387`, in Python 3.24 the existing modules will be removed -and code must use the ``compression`` sub-modules. The documentation for these -modules will be updated to discuss the planned deprecation and removal -timelines. +then the ``DeprecationWarning``s would be emitted in 3.19, the next release +after 3.13 reaches end of life. These warnings would begin five years after the +introduction of ``compression`` namespace. In accordance with :pep:`387`, in +Python 3.24, five years after the ``DeprecationWarning``s are added and ten +years after the new ``compression`` namespace is introduced, the existing +modules will be removed and code must use the ``compression`` sub-modules. The +documentation for these modules will be updated to discuss the planned +deprecation and removal timelines. Backwards Compatibility From 43171c4513cac03683a1ff971d3d67df34d8b9a8 Mon Sep 17 00:00:00 2001 From: Emma Harper Smith Date: Mon, 7 Apr 2025 18:25:04 -0700 Subject: [PATCH 3/3] Fix DeprecationWarnings --- peps/pep-0784.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/peps/pep-0784.rst b/peps/pep-0784.rst index e65db84d9ac..06326aae994 100644 --- a/peps/pep-0784.rst +++ b/peps/pep-0784.rst @@ -231,10 +231,10 @@ Compression module migration timeline Existing modules will emit a ``DeprecationWarning`` in the Python release following the last Python without the ``compression`` module leaving support. For example, if the ``compression`` namespace is introduced in 3.14, -then the ``DeprecationWarning``s would be emitted in 3.19, the next release +then the ``DeprecationWarnings`` would be emitted in 3.19, the next release after 3.13 reaches end of life. These warnings would begin five years after the introduction of ``compression`` namespace. In accordance with :pep:`387`, in -Python 3.24, five years after the ``DeprecationWarning``s are added and ten +Python 3.24, five years after the ``DeprecationWarnings`` are added and ten years after the new ``compression`` namespace is introduced, the existing modules will be removed and code must use the ``compression`` sub-modules. The documentation for these modules will be updated to discuss the planned