This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author scoder
Recipients Ramchandra Apte, abarnert, cameron, christian.heimes, cowlicks, georg.brandl, gregory.p.smith, gvanrossum, josh.r, martin.panter, ncoghlan, pitrou, rhettinger, scoder, serhiy.storchaka, socketpair, terry.reedy, vstinner
Date 2018-05-18.17:22:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526664124.27.0.682650639539.issue19251@psf.upfronthosting.co.za>
In-reply-to
Content
I'd second the proposal of considering the "array.array" type for this, instead of the bytes/bytearray types. Why? Because it is somewhat of a niche case after all, and the bytes type seems too exposed for it. Also, array.array supports more diverse base item types than just plain bytes, which could potentially cover more use cases or at least simplify certain data processing needs.

Alternatively, implement a lightweight SIMD-like memoryview type that operates on arbitrary buffers (which covers bytes, bytearray and array.array). But that's either NumPy then, or something new that would best spend its early days on PyPI.
History
Date User Action Args
2018-05-18 17:22:04scodersetrecipients: + scoder, gvanrossum, georg.brandl, rhettinger, terry.reedy, gregory.p.smith, ncoghlan, pitrou, vstinner, christian.heimes, cameron, socketpair, Ramchandra Apte, martin.panter, serhiy.storchaka, abarnert, josh.r, cowlicks
2018-05-18 17:22:04scodersetmessageid: <1526664124.27.0.682650639539.issue19251@psf.upfronthosting.co.za>
2018-05-18 17:22:04scoderlinkissue19251 messages
2018-05-18 17:22:04scodercreate