1 |
On Wed, 25 Jul 2018 23:23:18 -0400, allan gottlieb wrote: |
2 |
|
3 |
> On Thu, Jul 26 2018, Bill Kenworthy wrote: |
4 |
> |
5 |
> > On 26/07/18 09:10, allan gottlieb wrote: |
6 |
> >> I am still using python 3.4, i.e. |
7 |
> >> |
8 |
> >> sh-4.4# eselect python show |
9 |
> >> python3.4 |
10 |
> >> sh-4.4# |
11 |
> >> |
12 |
> >> sh-4.4# eselect python list |
13 |
> >> Available Python interpreters, in order of preference: |
14 |
> >> [1] python3.4 |
15 |
> >> [2] python3.6 (fallback) |
16 |
> >> [3] python3.5 (fallback) |
17 |
> >> [4] python2.7 (fallback) |
18 |
> >> sh-4.4# |
19 |
> >> |
20 |
> >> I realize I should have updated previously. |
21 |
> >> |
22 |
> >> Is a python update as simple as |
23 |
> >> emerge --update --changed-use --with-bdeps=n @world |
24 |
> >> eselect python set python3.6 |
25 |
> >> emerge --update --changed-use --with-bdeps=n @world |
26 |
> >> |
27 |
> >> I have no custom python scripts on either of my systems. |
28 |
> >> |
29 |
> >> thanks in advance, |
30 |
> >> allan |
31 |
> >> |
32 |
> > |
33 |
> > |
34 |
> > Hi, no problems doing it except because of the large number of |
35 |
> > packages look forward to hours of compiling (24hrs on my surface |
36 |
> > pro4). Got a few other systems to do which is going to take awhile. |
37 |
> > |
38 |
> > BillK |
39 |
> |
40 |
> Thank you, that is just what I needed to know. |
41 |
|
42 |
If the packages were already built with python_3.6 in PYTHON_TARGETS, |
43 |
there should be no rebuilding. It is the change on PYTHON_TARGETS that |
44 |
triggers the rebuild, eselect just chooses from one of the available |
45 |
targets AIUI. |
46 |
|
47 |
|
48 |
-- |
49 |
Neil Bothwick |
50 |
|
51 |
An unemployed Court Jester is nobody's fool. |