Message239101
| Author | serhiy.storchaka |
|---|---|
| Recipients | docs@python, ezio.melotti, martin.panter, r.david.murray, serhiy.storchaka |
| Date | 2015-03-24.09:20:16 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1427188816.9.0.00381696535261.issue23756@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Totally agree. Current definition is too wide. Actually in different places the term "bytes-like object" can imply different requirements.
* Supports buffer protocol. list isn't.
* Contiguous. memoryview()[::2] isn't.
* len() returns bytes size. array('I') isn't.
* Supported indexing (and slicing) of bytes. array('I') isn't.
* Indexing returns integers in the range 0-255. array('b') isn't.
* Supports concatenation. memoryview isn't.
* Supports common bytes and bytearray methods, such as find() or lower().
* A subclass of (bytes, bytearray).
* A subclass of bytes.
* A bytes itself. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-03-24 09:20:16 | serhiy.storchaka | set | recipients: + serhiy.storchaka, ezio.melotti, r.david.murray, docs@python, martin.panter |
| 2015-03-24 09:20:16 | serhiy.storchaka | set | messageid: <1427188816.9.0.00381696535261.issue23756@psf.upfronthosting.co.za> |
| 2015-03-24 09:20:16 | serhiy.storchaka | link | issue23756 messages |
| 2015-03-24 09:20:16 | serhiy.storchaka | create | |