[issue16724] Rename `data` argument names to `bytes`

R. David Murray added the comment: We do not use data type names as formal parameter names. You will realize this is sensible if you consider that in most cases in Python the formal parameter name is something gets used in more than just the documentation, and that using a type name would sha

[issue16724] Rename `data` argument names to `bytes`

Serhiy Storchaka added the comment: > If hexlify is not accepting anything except bytes, it is better be explicit. However hexlify is accepting something except bytes. It is accepting any object which supports buffer protocol. -- nosy: +serhiy.storchaka ___

[issue16724] Rename `data` argument names to `bytes`

Serhiy Storchaka added the comment: > If hexlify is not accepting anything except bytes, it is better be explicit. However hexlify is accepting something except bytes. It is accepting any object which supports buffer protocol. -- nosy: +serhiy.storchaka ___

[issue16724] Rename `data` argument names to `bytes`

Serhiy Storchaka added the comment: > If hexlify is not accepting anything except bytes, it is better be explicit. However hexlify is accepting something except bytes. It is accepting any object which supports buffer protocol. -- nosy: +serhiy.storchaka ___

[issue16724] Rename `data` argument names to `bytes`

Amaury Forgeot d'Arc added the comment: > When people use docs as a reference, they don't read top notes. Maybe, but they can read some words beyond the function name, can't they? -- ___ Python tracker

[issue16724] Rename `data` argument names to `bytes`

anatoly techtonik added the comment: Fact no.1: When people use docs as a reference, they don't read top notes. Face no.2: This is not explicit: binascii.hexlify(data) This is: binascii.hexlify(bytes) I understand that you like the wording in description, but can't understand why don't wan

[issue16724] Rename `data` argument names to `bytes`

Andrew Svetlov added the comment: I agree: the docs is good and don't needed to be modified. -- nosy: +asvetlov ___ Python tracker ___ ___

[issue16724] Rename `data` argument names to `bytes`

Amaury Forgeot d'Arc added the comment: > If hexlify is not accepting anything except bytes, it is better be explicit. But it is very explicit in the link you provided: both a note at the top, and the words "binary data" in the description of every function. -- ___

[issue16724] Rename `data` argument names to `bytes`

Amaury Forgeot d'Arc added the comment: > If hexlify is not accepting anything except bytes, it is better be explicit. But it is very explicit in the link you provided: both a note at the top, and the words "binary data" in the description of every function. -- ___

[issue16724] Rename `data` argument names to `bytes`

anatoly techtonik added the comment: In Python 2 there was no 'binary data' type - everything was a string. Now we have string, str, bytearray, array, list of ints. If hexlify is not accepting anything except bytes, it is better be explicit. When porting code from Python 2 the argument was pas

[issue16724] Rename `data` argument names to `bytes`

Amaury Forgeot d'Arc added the comment: Why? The binascii module consistently uses "data" to refer to binary data. For example: "Return the hexadecimal representation of the binary data. Every byte of data is converted ..." -- nosy: +amaury.forgeotdarc ___

[issue16724] Rename `data` argument names to `bytes`

New submission from anatoly techtonik: http://docs.python.org/3/library/binascii - binascii.hexlify(data) + binascii.hexlify(bytes) tag:easy -- assignee: docs@python components: Documentation messages: 177727 nosy: docs@python, techtonik priority: normal severity: normal status: open t