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