While sys-libs/libselinux properly creates a selinux directory with module files in /usr/lib64/python2.7/site-packages/, all python tools that depend on this module are broken, and spit out the error "no module named _selinux". As seen on https://bugzilla.redhat.com/show_bug.cgi?id=1349954, this is probably an incompatibility with new versions of swig. The workaround on one of those posts, (coping _selinux.so to /usr/lib64/python2.7/site-packages, in other words bringing it out of the selinux directory) works around the issue.
upstream does exactly that now https://github.com/SELinuxProject/selinux/commit/a9604c30a5e2f71007d31aa6ba41cf7b95d94822
Are there any news on this?
I just pushed libselinux-2.5-r1 to the tree with this patch backported.