Serhiy Storchaka added the comment: What is wrong? ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________

Марк Коренберг added the comment: I mean when signed=True ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________

Марк Коренберг added the comment: Well. Phrase `If signed is False and a negative integer is given, an OverflowError is raised.` describe onlyhalf of behaviour. It does not explain behaviour when `signed=True` and value is big enough to trigger exception, but not enough to trigger it when signed=False. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________

INADA Naoki added the comment: @mmarkk Do you read full docstring? It's documented very clearly. --- int.to_bytes(length, byteorder, *, signed=False) -> bytes Return an array of bytes representing an integer. The integer is represented using length bytes. An OverflowError is raised if the integer is not representable with the given number of bytes. The byteorder argument determines the byte order used to represent the integer. If byteorder is 'big', the most significant byte is at the beginning of the byte array. If byteorder is 'little', the most significant byte is at the end of the byte array. To request the native byte order of the host system, use `sys.byteorder' as the byte order value. The signed keyword-only argument determines whether two's complement is used to represent the integer. If signed is False and a negative integer is given, an OverflowError is raised. --- ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________

R. David Murray added the comment: Looks correct to me as well. If you can think of a wording that would be clearer, Марк, that would be great, but it shouldn't make the docstring much wordier (we strive for conciseness in docstrings). That the last phrase can't be just removed without omitting an important piece of information (an *additional* time OverflowError can be raised). ---------- nosy: +r.david.murray _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________

Changes by R. David Murray <rdmurray@bitdance.com>: ---------- Removed message: http://bugs.python.org/msg271381 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue27622> _______________________________________