From 1f196ea6c37d9c9264e16c985a42f885aa7b958e Mon Sep 17 00:00:00 2001 From: Ethan Furman Date: Wed, 27 Dec 2023 11:51:37 -0800 Subject: [PATCH] PEP-0467: include reference to current iter-bytes thread (GH-3608) --- peps/pep-0467.rst | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/peps/pep-0467.rst b/peps/pep-0467.rst index d410bcc72..188007b0e 100644 --- a/peps/pep-0467.rst +++ b/peps/pep-0467.rst @@ -9,7 +9,7 @@ Content-Type: text/x-rst Created: 30-Mar-2014 Python-Version: 3.12 Post-History: 30-Mar-2014, 15-Aug-2014, 16-Aug-2014, 07-Jun-2016, 01-Sep-2016, - 13-Apr-2021, 03-Nov-2021 + 13-Apr-2021, 03-Nov-2021, 27-Dec-2023 Abstract @@ -177,6 +177,13 @@ that ``bytes(x)`` (where ``x`` is an integer) should behave like the ``bytes.fromint(x)`` proposal in this PEP. Providing both behaviors as separate class methods avoids that ambiguity. +Current Workarounds +------------------- + +After nearly a decade, there's seems to be no consensus on the best workarounds +for byte iteration, as demonstrated by +`Get single-byte bytes objects from bytes objects`_. + Omitting the originally proposed builtin function ------------------------------------------------- @@ -211,7 +218,7 @@ References * `Issue proposing to use calloc() for zero-initialised binary sequences `_ * `August 2014 discussion thread on python-dev `_ * `June 2016 discussion thread on python-dev `_ - +* `Get single-byte bytes objects from bytes objects `_ Copyright =========