PEP 798: Add SC acceptance requirement

Author: hugovk

peps/pep-0798.rst

@@ -13,6 +13,26 @@ Post-History:
   `19-Jul-2025 <https://discuss.python.org/t/pep-798-unpacking-in-comprehensions/99435>`__,
 Resolution: `03-Nov-2025 <https://discuss.python.org/t/pep-798-unpacking-in-comprehensions/99435/60>`__
 
+.. note::
+   The Steering Council accepts this PEP with one modification: we require that
+   both synchronous and asynchronous generator expressions use explicit loops
+   rather than yield from for unpacking operations.
+
+   The Steering Council believes that simplicity and consistency are paramount
+   here. The delegation behaviour provided by ``yield from`` adds semantic
+   complexity for advanced use cases involving ``.send(),`` ``.throw()``, and
+   ``.close()`` that are rarely relevant when writing comprehensions. We don’t
+   believe that developers writing comprehensions should have to think about
+   the differences between sync and async generator semantics or about generator
+   delegation protocols. We firmly believe that the mental model should be as
+   simple as possible and as symmetric as possible between all kinds of
+   comprehensions. The straightforward semantics of explicit loops provide a
+   uniform mental model that works the same way regardless of context, and also
+   provides better parity with the function-like versions, such as
+   ``itertools.chain.from_iterable``. For the rare cases where someone actually
+   needs delegation behaviour, the Steering Council believes they should use an
+   explicit generator function with ``yield from`` rather than a comprehension.
+
 
 Abstract
 ========