PEP-0467: include reference to current iter-bytes thread (GH-3608)
This commit is contained in:
parent
d119fc4129
commit
1f196ea6c3
|
@ -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 <https://github.com/python/cpython/issues/65843>`_
|
||||
* `August 2014 discussion thread on python-dev <https://mail.python.org/pipermail/python-ideas/2014-March/027295.html>`_
|
||||
* `June 2016 discussion thread on python-dev <https://mail.python.org/pipermail/python-dev/2016-June/144875.html>`_
|
||||
|
||||
* `Get single-byte bytes objects from bytes objects <https://discuss.python.org/t/get-single-byte-bytes-objects-from-a-bytes-object/41709>`_
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
|
Loading…
Reference in New Issue