(original) (raw)

On 18 Aug 2014 08:55, "Barry Warsaw" <barry@python.org> wrote:
\>
\> On Aug 18, 2014, at 08:48 AM, Nick Coghlan wrote:
\>
\> >Calling it bytes is too confusing:
\> >
\> > for x in bytes(data):
\> > ...
\> >
\> > for x in bytes(data).bytes()
\> >
\> >When referring to bytes, which bytes do you mean, the builtin or the method?
\> >
\> >iterbytes() isn't especially attractive as a method name, but it's far more
\> >explicit about its purpose.
\>
\> I don't know. How often do you really instantiate the bytes object there in
\> the for loop?

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?

Namespaces are great and all, but using the same name for two different concepts is still inherently confusing.

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
\>