Comment # 2 on bug 1029902 from Jan Matejek

this happens when running python 3.6.0 built on a newer (>=3.17) kernel running
on older kernel.

As a workaround, you can build python3 on the same configuration and the
resulting package will work fine.

The problem will be fixed by updating to 3.6.1, which is expected to release
today.