[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

Josh Rosenberg added the comment: The description is nonsensical as is; not sure the patch goes far enough. C-style strings are *defined* to end at the NUL terminator; if it really needs a NUL after the int, saying it "points to the first character which follows the representation of the

[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

Change by Henk-Jaap Wagenaar : -- nosy: +Cryvate nosy_count: 4.0 -> 5.0 pull_requests: +25360 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26774 ___ Python tracker

[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

Change by Henk-Jaap Wagenaar : -- nosy: +cryvate ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

Change by Irit Katriel : -- keywords: +easy type: -> enhancement versions: +Python 3.11 ___ Python tracker ___ ___

[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

Chris Angelico added the comment: Patch doesn't apply to current Python trunk (18 months later). Do you know what version you wrote this against? The current wording is different. -- nosy: +Rosuav ___ Python tracker rep...@bugs.python.org

[issue14995] PyLong_FromString documentation should state that the string must be null-terminated

New submission from Ryan Kelly r...@rfk.id.au: PyLong_FromString will raise a ValueError if the given string doesn't contain a null byte after the digits. For example, this will result in a ValueError char *pend; PyLong_FromString(1234 extra, pend, 10) While this will successfully read