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