On 03/02/2012 11:24 AM, Dale wrote: > But if I tell eselect to set it to 3 something then that is what the > system will try to use right?
"The system" isn't granular enough (I've been dying to use that geek- speak phrase :) when discussing portage, which is only part of a gentoo "system". List the files in sys-apps/portage and you'll see that none of them go in /usr/lib/pythonN.N/site-packages like mere ordinary python packages. They go instead in /usr/lib/portage, which is independent of your python version. However, try this trick: #head -1 /usr/lib/portage/bin/emerge #!/usr/bin/python3 You can see from that I've installed portage to use python3, even though: #eselect python list Available Python interpreters: [1] python2.7 * [2] python3.1 I still have my "system" python set to 2.7 like most of us, I suspect. At this point, the portage package obeys the setting of the python3 useflag to decide which python to use and I have my python3 useflag set, so portage announces "fixing shebangs" at the end of the emerge, and that's where the #!/usr/bin/python3 comes from.
