Mark Knecht wrote: > On Fri, Mar 2, 2012 at 3:36 AM, Dale <[email protected]> wrote: >> Howdy, >> >> I'm just wanting to make certain I don't break my rig. Info first: >> >> root@fireball / # eselect python list >> Available Python interpreters: >> [1] python2.7 * >> [2] python3.1 >> [3] python3.2 >> root@fireball / # >> >> I ran --depclean and it wants to remove python 3.1. I ran python >> updater and recompiled the needed packages. Since python 2.7 is the >> default python, is it safe to remove python 3.1? As we all know, python >> and portage is really good friends and portage gets real upset when it >> looses its friend. I'd much rather ask this question than have to start >> a thread on how to repair python with a dead portage. >> >> So, safe to remove? I'm thinking it is but just want the comfort of >> taking someone else with me it is breaks. lol >> >> Dale >> > > You should be safe but please do an > > eselect python list --python3 > > and make sure you're set to 3.2 before removing 3.1. > > HTH, > Mark > >
Last I heard we are not supposed to set python to 3 anything. Has that changed? Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
