SELinux Handbook tells people to switch to python2, but when installing from recent stages python2 is not present at all on the system. The guide should tell people to install python2 if it's missing: emerge --noreplace python:2.7
Doesn't it pull this in automatically? We package.use.force USE="python2" for portage in our profiles. That said, we might want to verify if python3 now works fully on SELinux or not. Recent userland utilities already have some Python-3 changes in them (currently marked as ~arch, ETA stabilization 20120430).
(In reply to comment #1) > Doesn't it pull this in automatically? I don't know - the stage3 didn't contain python2, and the SELinux Handbook has the following order of operations: 1. eselect python set ... 2. eselect profile set ... 3. emerge -uDNa world Only step #3 has the potential to pull in python2, and I've just done it manually before #1. > We package.use.force USE="python2" for portage in our profiles. Now emerge --depclean --verbose --pretend python:2.7 shows that it's pulled by portage, among others.
Fixed in CVS
