Message274724
| Author | vstinner |
|---|---|
| Recipients | martin.panter, ncoghlan, python-dev, vstinner |
| Date | 2016-09-07.03:03:43 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1473217423.31.0.880210152384.issue27778@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> 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? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-09-07 03:03:43 | vstinner | set | recipients: + vstinner, ncoghlan, python-dev, martin.panter |
| 2016-09-07 03:03:43 | vstinner | set | messageid: <1473217423.31.0.880210152384.issue27778@psf.upfronthosting.co.za> |
| 2016-09-07 03:03:43 | vstinner | link | issue27778 messages |
| 2016-09-07 03:03:43 | vstinner | create | |