[Python-Dev] Adding bytes.frombuffer() constructor to PEP 467
Antoine Pitrou
solipsis at pitrou.net
Fri Jan 6 07:03:46 EST 2017
More information about the Python-Dev mailing list
Fri Jan 6 07:03:46 EST 2017
- Previous message (by thread): [Python-Dev] Context manager lifetime rules Was: Re: Adding bytes.frombuffer() constructor to PEP 467
- Next message (by thread): [Python-Dev] Adding bytes.frombuffer() constructor to PEP 467
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 5 Jan 2017 20:28:26 -0500 Yury Selivanov <yselivanov.ml at gmail.com> wrote: > On 2017-01-05 7:11 PM, INADA Naoki wrote: > >> bytes.frombuffer(x) is bytes(memoryview(x)) or memoryview(x).tobytes(). > >> > > There is pitfall: memoryview should be closed. > > So b = bytes.frombuffer(x) is: > > > > with memoryview(x) as m: > > b = bytes(m) > > # or b = m.tobytes() > > Thinking more about this, and after looking at my own code in asyncpg > and uvloop, I'm now in favor of adding bytes.frombuffer() with the > proposed signature: ``bytes.frombuffer(byteslike, length=-1, offset=0)`` +1 Note this matches numpy.frombuffer(): """ frombuffer(buffer, dtype=float, count=-1, offset=0) Interpret a buffer as a 1-dimensional array. """ Regards Antoine.
- Previous message (by thread): [Python-Dev] Context manager lifetime rules Was: Re: Adding bytes.frombuffer() constructor to PEP 467
- Next message (by thread): [Python-Dev] Adding bytes.frombuffer() constructor to PEP 467
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list