(original) (raw)

On 18 Aug 2014 09:57, "Barry Warsaw" <barry@python.org> wrote:
\>
\> On Aug 18, 2014, at 09:12 AM, Nick Coghlan wrote:
\>
\> >I'm talking more generally - do you \*really\* want to be explaining that
\> >"bytes" behaves like a tuple of integers, while "bytes.bytes" behaves like
\> >a tuple of bytes?
\>
\> I would explain it differently though, using concrete examples.
\>
\> data = bytes(...)
\> for i in data: # iterate over data as integers
\> for i in data.bytes: # iterate over data as bytes
\>
\> But whatever. I just wish there was something better than iterbytes.

There's actually another aspect to your idea, independent of the naming: exposing a view rather than just an iterator. I'm going to have to look at the implications for memoryview, but it may be a good way to go (and would align with the iterator -> view changes in dict).

Cheers,
Nick.

>
\> -Barry
\>
\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\> Python-Dev mailing list
\> Python-Dev@python.org
\> https://mail.python.org/mailman/listinfo/python-dev
\> Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
\>