| 1 |
On Fri, Mar 2, 2012 at 11:24 AM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Mark Knecht wrote: |
| 3 |
>> On Fri, Mar 2, 2012 at 10:20 AM, Dale <rdalek1967@×××××.com> wrote: |
| 4 |
>>> Mark Knecht wrote: |
| 5 |
>>>> On Fri, Mar 2, 2012 at 3:36 AM, Dale <rdalek1967@×××××.com> wrote: |
| 6 |
>>>>> Howdy, |
| 7 |
>>>>> |
| 8 |
>>>>> I'm just wanting to make certain I don't break my rig. Info first: |
| 9 |
>>>>> |
| 10 |
>>>>> root@fireball / # eselect python list |
| 11 |
>>>>> Available Python interpreters: |
| 12 |
>>>>> [1] python2.7 * |
| 13 |
>>>>> [2] python3.1 |
| 14 |
>>>>> [3] python3.2 |
| 15 |
>>>>> root@fireball / # |
| 16 |
>>>>> |
| 17 |
>>>>> I ran --depclean and it wants to remove python 3.1. I ran python |
| 18 |
>>>>> updater and recompiled the needed packages. Since python 2.7 is the |
| 19 |
>>>>> default python, is it safe to remove python 3.1? As we all know, python |
| 20 |
>>>>> and portage is really good friends and portage gets real upset when it |
| 21 |
>>>>> looses its friend. I'd much rather ask this question than have to start |
| 22 |
>>>>> a thread on how to repair python with a dead portage. |
| 23 |
>>>>> |
| 24 |
>>>>> So, safe to remove? I'm thinking it is but just want the comfort of |
| 25 |
>>>>> taking someone else with me it is breaks. lol |
| 26 |
>>>>> |
| 27 |
>>>>> Dale |
| 28 |
>>>>> |
| 29 |
>>>> |
| 30 |
>>>> You should be safe but please do an |
| 31 |
>>>> |
| 32 |
>>>> eselect python list --python3 |
| 33 |
>>>> |
| 34 |
>>>> and make sure you're set to 3.2 before removing 3.1. |
| 35 |
>>>> |
| 36 |
>>>> HTH, |
| 37 |
>>>> Mark |
| 38 |
>>>> |
| 39 |
>>>> |
| 40 |
>>> |
| 41 |
>>> |
| 42 |
>>> Last I heard we are not supposed to set python to 3 anything. Has that |
| 43 |
>>> changed? |
| 44 |
>>> |
| 45 |
>>> Dale |
| 46 |
>>> |
| 47 |
>> |
| 48 |
>> No, we're not supposed to set the *system* *default* to python3 yet. |
| 49 |
>> Still, if you have multiple 3.x versions installed you would want to |
| 50 |
>> set the python3 setting to the python version you want to default to |
| 51 |
>> should some program absolutely require python3, so we've got 3 real |
| 52 |
>> settings: |
| 53 |
>> |
| 54 |
>> System default - still python-2.x |
| 55 |
>> Python2 - same python-2.x version as the system default |
| 56 |
>> Python3 - what ever version you want for programs requiring Python3 |
| 57 |
>> |
| 58 |
>> HTH, |
| 59 |
>> Mark |
| 60 |
>> |
| 61 |
>> |
| 62 |
> |
| 63 |
> |
| 64 |
> But if I tell eselect to set it to 3 something then that is what the |
| 65 |
> system will try to use right? Isn't that what eselect does? I'm |
| 66 |
> recalling what was posted after you emerge python here. The einfo/ewarn |
| 67 |
> thingy. |
| 68 |
> |
| 69 |
> Again, this may have changed but what I'm wondering is if we need the |
| 70 |
> python 2 stuff any more if we can set this to python 3. After all, |
| 71 |
> python 2 has to die eventually. ^_^ |
| 72 |
> |
| 73 |
> Dale |
| 74 |
|
| 75 |
Dale, |
| 76 |
I'll try to make it clearer: |
| 77 |
|
| 78 |
The command "eselect python set #" sets the system python profile. |
| 79 |
This command allows you to choose any python currently on your system. |
| 80 |
You should only choose a python2 setting at this time. |
| 81 |
|
| 82 |
The commands: |
| 83 |
eselect python list --python2 |
| 84 |
eselect python set --python2 # |
| 85 |
|
| 86 |
only deal with python2 |
| 87 |
|
| 88 |
The command |
| 89 |
eselect python list --python3 |
| 90 |
eselect python set --python3 # |
| 91 |
|
| 92 |
only deal with python3 |
| 93 |
|
| 94 |
All three of those profiles (python, python2 & python3) are distinct |
| 95 |
entities. They are different and can each be set any way you want. I |
| 96 |
was only clarifying that before you removed python3.1 that you choose |
| 97 |
python3.2 for your python3 profile. |
| 98 |
|
| 99 |
Clearer? |
| 100 |
|
| 101 |
HTH, |
| 102 |
Mark |
Archives