On 24/03/2016 19:19, Peter Humphrey wrote: > On Thursday 24 March 2016 11:54:03 Dale wrote: > >> I'm not sure if this has changed but I think it used to be recommended >> not to set Python 3 stuff to active, at the time anyway. That may have >> changed. I read that either here or on -dev a good while back. May >> want to see what others think on this or it could be that everything you >> use works fine that way. > > I saw that too, and I've always been sure to eselect python to 2.7, but for > a long time now the installation CD has come with 3.3 or 3.4 set, so I > assume it's okay to eselect 3.4 nowadays. >
It's probably not safe, python2 and python3 are basically different languages, not really compatible. Out there in the wild, there are still more python apps not migrated to use python3 than have been migrated. A user has 2 choices: - set python2 as default and configure packages that can use python3 to use it - set python3 as default and configure packages that requires python2 to use it Which method you use depends entirely on what packages you use. -- Alan McKinnon [email protected]
