[issue15213] _PyOS_URandom documentation

Roundup Robot added the comment: New changeset 176bb5a98463 by Georg Brandl in branch '3.3': Closes #15213: update comment for _PyOS_URandom http://hg.python.org/cpython/rev/176bb5a98463 -- ___ Python tracker _

[issue15213] _PyOS_URandom documentation

Roundup Robot added the comment: New changeset 3e5078c3784e by Georg Brandl in branch '2.7': Closes #15213: update comment for _PyOS_URandom http://hg.python.org/cpython/rev/3e5078c3784e -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue15213] _PyOS_URandom documentation

STINNER Victor added the comment: > The comment needs to be fixed before the issue is closed. Ah yes, here is a patch updating the comment of _PyOS_URandom() and the doc of the os module. -- keywords: +patch Added file: http://bugs.python.org/file26650/urandom_doc.patch ___

[issue15213] _PyOS_URandom documentation

Antoine Pitrou added the comment: The comment needs to be fixed before the issue is closed. -- ___ Python tracker ___ ___ Python-bugs-

[issue15213] _PyOS_URandom documentation

STINNER Victor added the comment: So can we close this issue, or should we start to document private functions? -- ___ Python tracker ___

[issue15213] _PyOS_URandom documentation

Martin v. Löwis added the comment: It's not an official API, as the leading underscore specifies. Changing the comment sounds fine to me. -- nosy: +loewis ___ Python tracker __

[issue15213] _PyOS_URandom documentation

New submission from Christian Heimes : The comment for Python/random.c:_PyOS_URandom() states > Fill buffer with size pseudo-random bytes, not suitable for cryptographic > use, from the operating random number generator (RNG). which is not correct as all paths use a RNG that is suitable for mo