From 3461e29bb36c97080891a981e1aef8f5ac7b702a Mon Sep 17 00:00:00 2001 From: William Woodruff Date: Mon, 2 Nov 2026 10:51:44 -0500 Subject: [PATCH 1/2] PEP 847: add some context around multiple errors Signed-off-by: William Woodruff --- peps/pep-0847.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/peps/pep-0847.rst b/peps/pep-0847.rst index 2a34ced28c4..1ef6298ff6b 100644 --- a/peps/pep-0847.rst +++ b/peps/pep-0847.rst @@ -263,7 +263,8 @@ Another option is to diverge from :rfc:`9457`, and pick (or invent) another error format. An argument in favor of this is specificity: a custom error format could, for example, provide dedicated error codes that communicate failure modes that are common/shared -across many index implementations and hosts. +across many index implementations and hosts. Similarly, a custom error +format could represent multiple errors from an index at once. We consider this option unsuitable for two reasons: @@ -272,8 +273,10 @@ We consider this option unsuitable for two reasons: need custom representations for various authorization and authentication error states. #. :rfc:`9457` is *already* extensible, and a future PEP *could* added shared error - codes as a well-known extension in the future. In other words, any foreseeable - benefit from a custom format is already subsumable within the Problem Details format. + codes as a well-known extension in the future. Similarly, :rfc:`9457`'s design + enabled multiple interior errors as an extension, per :rfc:`9457#section-3`. + In other words, the benefits of a custom format are already provided by the + Problem Details format. .. _problem-details-appendix-1: From 0086a545478901c0c2d648d003f7bd17be2701a8 Mon Sep 17 00:00:00 2001 From: William Woodruff Date: Mon, 2 Nov 2026 10:53:29 -0500 Subject: [PATCH 2/2] Typo Signed-off-by: William Woodruff --- peps/pep-0847.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/peps/pep-0847.rst b/peps/pep-0847.rst index 1ef6298ff6b..297481fe3f6 100644 --- a/peps/pep-0847.rst +++ b/peps/pep-0847.rst @@ -274,7 +274,7 @@ We consider this option unsuitable for two reasons: states. #. :rfc:`9457` is *already* extensible, and a future PEP *could* added shared error codes as a well-known extension in the future. Similarly, :rfc:`9457`'s design - enabled multiple interior errors as an extension, per :rfc:`9457#section-3`. + enables multiple interior errors as an extension, per :rfc:`9457#section-3`. In other words, the benefits of a custom format are already provided by the Problem Details format.