467: update deprecation and memoryview statements
This commit is contained in:
parent
69d0e87ccf
commit
28c4f3304f
16
pep-0467.txt
16
pep-0467.txt
|
@ -58,7 +58,7 @@ of the given size::
|
|||
bytearray(b'\x00\x00\x00')
|
||||
|
||||
This PEP proposes to update the documentation to discourage making use of that
|
||||
input type dependent behaviour in Python 3.9, suggesting to use a new, more
|
||||
input type dependent behaviour in Python 3.10, suggesting to use a new, more
|
||||
explicit, ``bytes.fromsize(n)`` or ``bytearray.fromsize(n)`` spelling instead
|
||||
(see next section).
|
||||
|
||||
|
@ -208,17 +208,11 @@ This is for consistency with the other methods on the affected types, and to
|
|||
avoid having to devise sensible names for them.
|
||||
|
||||
|
||||
Open Questions
|
||||
==============
|
||||
Open Issue: memoryview
|
||||
======================
|
||||
|
||||
* Given the "multiple ways to do it" outcome, is the proposed ``bchr`` builtin
|
||||
actually worth adding, or is ``ord``/``bytes.fromord``/``chr`` a sufficiently
|
||||
straightforward replacement for the Python 2 ``ord``/``chr``/``unichr``
|
||||
operations?
|
||||
|
||||
* Do we add ``iterbytes`` to ``memoryview``, or modify
|
||||
``memoryview.cast()`` to accept ``'s'`` as a single-byte interpretation? Or
|
||||
do we ignore ``memoryview`` for now and add it later?
|
||||
Updating ``memoryview`` with these new methods is outside the scope of this PEP.
|
||||
>>>>>>> 467: update deprecation and memoryview statements
|
||||
|
||||
|
||||
References
|
||||
|
|
Loading…
Reference in New Issue