On Wed, 25 Jul 2018 23:23:18 -0400, allan gottlieb wrote:

> On Thu, Jul 26 2018, Bill Kenworthy wrote:
> 
> > On 26/07/18 09:10, allan gottlieb wrote:  
> >> I am still using python 3.4, i.e.
> >>
> >>   sh-4.4# eselect python show
> >>   python3.4
> >>   sh-4.4# 
> >>
> >>   sh-4.4# eselect python list
> >>   Available Python interpreters, in order of preference:
> >>     [1]   python3.4
> >>     [2]   python3.6 (fallback)
> >>     [3]   python3.5 (fallback)
> >>     [4]   python2.7 (fallback)
> >>   sh-4.4# 
> >>   
> >> I realize I should have updated previously.
> >>
> >> Is a python update as simple as
> >>   emerge --update --changed-use --with-bdeps=n @world
> >>   eselect python set python3.6
> >>   emerge --update --changed-use --with-bdeps=n @world
> >>
> >> I have no custom python scripts on either of my systems.
> >>
> >> thanks in advance,
> >> allan
> >>  
> >
> >
> > Hi, no problems doing it except because of the large number of
> > packages look forward to hours of compiling (24hrs on my surface
> > pro4).  Got a few other systems to do which is going to take awhile.
> >
> > BillK  
> 
> Thank you, that is just what I needed to know.

If the packages were already built with python_3.6 in PYTHON_TARGETS,
there should be no rebuilding. It is the change on PYTHON_TARGETS that
triggers the rebuild, eselect just chooses from one of the available
targets AIUI.


-- 
Neil Bothwick

An unemployed Court Jester is nobody's fool.