STINNER Victor added the comment: > HAVE_GETRANDOM_SYSCALL seems to be a compile-time library check, not a > runtime check. I compiled and run on Linux 3.15.5, and os.getrandom() exists > but raises ENOSYS:
Oh, I'm surprised the configure sees getrandom() as available. But well ok, the error can occur if you compile Python on a more recent kernel than the running kernel. I fixed the unit test: skip getrandom() tests if getrandom() fails with ENOSYS. Do you think that it's worth to document this case? ---------- resolution: fixed -> status: closed -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27778> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
