Howdy,

I'm just wanting to make certain I don't break my rig. Info first:

root@fireball / # eselect python list
Available Python interpreters:
[1] python2.7 *
[2] python3.1
[3] python3.2
root@fireball / #

I ran --depclean and it wants to remove python 3.1. I ran python
updater and recompiled the needed packages. Since python 2.7 is the
default python, is it safe to remove python 3.1? As we all know, python
and portage is really good friends and portage gets real upset when it
looses its friend. I'd much rather ask this question than have to start
a thread on how to repair python with a dead portage.

So, safe to remove? I'm thinking it is but just want the comfort of
taking someone else with me it is breaks. lol

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Dale wrote:
> Howdy,
>
> I'm just wanting to make certain I don't break my rig. Info first:
>
> root@fireball / # eselect python list
> Available Python interpreters:
> [1] python2.7 *
> [2] python3.1
> [3] python3.2
> root@fireball / #
>
> I ran --depclean and it wants to remove python 3.1. I ran python
> updater and recompiled the needed packages. Since python 2.7 is the
> default python, is it safe to remove python 3.1? As we all know, python
> and portage is really good friends and portage gets real upset when it
> looses its friend. I'd much rather ask this question than have to start
> a thread on how to repair python with a dead portage.
>
> So, safe to remove? I'm thinking it is but just want the comfort of
> taking someone else with me it is breaks. lol
>
> Dale
>
> :-) :-)
>


I really need to not post when I take my meds. lol The last line
should read "* someone else with me if it breaks."

Meds. They help some things but hurt other things. o_O

Thanks.

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Dale writes:

> root@fireball / # eselect python list
> Available Python interpreters:
> [1] python2.7 *
> [2] python3.1
> [3] python3.2
> root@fireball / #
>
> I ran --depclean and it wants to remove python 3.1. I ran python
> updater and recompiled the needed packages. Since python 2.7 is the
> default python, is it safe to remove python 3.1? As we all know, python
> and portage is really good friends and portage gets real upset when it
> looses its friend. I'd much rather ask this question than have to start
> a thread on how to repair python with a dead portage.
>
> So, safe to remove? I'm thinking it is but just want the comfort of
> taking someone else with me it is breaks. lol

It's safe, your portage uses 2.7.

Wonko

Alex Schuster wrote:
> Dale writes:
>
>> root@fireball / # eselect python list
>> Available Python interpreters:
>> [1] python2.7 *
>> [2] python3.1
>> [3] python3.2
>> root@fireball / #
>>
>> I ran --depclean and it wants to remove python 3.1. I ran python
>> updater and recompiled the needed packages. Since python 2.7 is the
>> default python, is it safe to remove python 3.1? As we all know, python
>> and portage is really good friends and portage gets real upset when it
>> looses its friend. I'd much rather ask this question than have to start
>> a thread on how to repair python with a dead portage.
>>
>> So, safe to remove? I'm thinking it is but just want the comfort of
>> taking someone else with me it is breaks. lol
>
> It's safe, your portage uses 2.7.
>
> Wonko
>
>


Thanks for the confirmation. I was thinking it was but wanted to double
check.

Thanks again.

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

On Fri, Mar 2, 2012 at 3:36 AM, Dale <rdalek1967@gmail.com> wrote:
> Howdy,
>
> I'm just wanting to make certain I don't break my rig. *Info first:
>
> root@fireball / # eselect python list
> Available Python interpreters:
> *[1] * python2.7 *
> *[2] * python3.1
> *[3] * python3.2
> root@fireball / #
>
> I ran --depclean and it wants to remove python 3.1. *I ran python
> updater and recompiled the needed packages. *Since python 2.7 is the
> default python, is it safe to remove python 3.1? *As we all know, python
> and portage is really good friends and portage gets real upset when it
> looses its friend. *I'd much rather ask this question than have to start
> a thread on how to repair python with a dead portage.
>
> So, safe to remove? *I'm thinking it is but just want the comfort of
> taking someone else with me it is breaks. *lol
>
> Dale
>

You should be safe but please do an

eselect python list --python3

and make sure you're set to 3.2 before removing 3.1.

HTH,
Mark

On 2012-03-02 9:28 AM, Mark Knecht <markknecht@gmail.com> wrote:

eselect python list --python3

and make sure you're set to 3.2 before removing 3.1.


Hmmm... mine shows it is set to 3.1...

# eselect python list --python3
Available Python 3 interpreters:
[1] python3.1 *
[2] python3.2
myhost : Fri Mar 02, 13:07:51 : ~
#

So, that would be

eselect python set --python3 2

to set it to 3.2 leaving 2.7 as the main active python, right?

Just making sure because I know that mucking up python is *not* a
problem I want to have to deal with...

Mark Knecht wrote:
> On Fri, Mar 2, 2012 at 3:36 AM, Dale <rdalek1967@gmail.com> wrote:
>> Howdy,
>>
>> I'm just wanting to make certain I don't break my rig. Info first:
>>
>> root@fireball / # eselect python list
>> Available Python interpreters:
>> [1] python2.7 *
>> [2] python3.1
>> [3] python3.2
>> root@fireball / #
>>
>> I ran --depclean and it wants to remove python 3.1. I ran python
>> updater and recompiled the needed packages. Since python 2.7 is the
>> default python, is it safe to remove python 3.1? As we all know, python
>> and portage is really good friends and portage gets real upset when it
>> looses its friend. I'd much rather ask this question than have to start
>> a thread on how to repair python with a dead portage.
>>
>> So, safe to remove? I'm thinking it is but just want the comfort of
>> taking someone else with me it is breaks. lol
>>
>> Dale
>>
>
> You should be safe but please do an
>
> eselect python list --python3
>
> and make sure you're set to 3.2 before removing 3.1.
>
> HTH,
> Mark
>
>


Last I heard we are not supposed to set python to 3 anything. Has that
changed?

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

On Fri, Mar 2, 2012 at 10:20 AM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>> On Fri, Mar 2, 2012 at 3:36 AM, Dale <rdalek1967@gmail.com> wrote:
>>> Howdy,
>>>
>>> I'm just wanting to make certain I don't break my rig. *Info first:
>>>
>>> root@fireball / # eselect python list
>>> Available Python interpreters:
>>> *[1] * python2.7 *
>>> *[2] * python3.1
>>> *[3] * python3.2
>>> root@fireball / #
>>>
>>> I ran --depclean and it wants to remove python 3.1. *I ran python
>>> updater and recompiled the needed packages. *Since python 2.7 is the
>>> default python, is it safe to remove python 3.1? *As we all know, python
>>> and portage is really good friends and portage gets real upset when it
>>> looses its friend. *I'd much rather ask this question than have to start
>>> a thread on how to repair python with a dead portage.
>>>
>>> So, safe to remove? *I'm thinking it is but just want the comfort of
>>> taking someone else with me it is breaks. *lol
>>>
>>> Dale
>>>
>>
>> You should be safe but please do an
>>
>> eselect python list --python3
>>
>> and make sure you're set to 3.2 before removing 3.1.
>>
>> HTH,
>> Mark
>>
>>
>
>
> Last I heard we are not supposed to set python to 3 anything. *Has that
> changed?
>
> Dale
>

No, we're not supposed to set the *system* *default* to python3 yet.
Still, if you have multiple 3.x versions installed you would want to
set the python3 setting to the python version you want to default to
should some program absolutely require python3, so we've got 3 real
settings:

System default - still python-2.x
Python2 - same python-2.x version as the system default
Python3 - what ever version you want for programs requiring Python3

HTH,
Mark

Mark Knecht wrote:
> On Fri, Mar 2, 2012 at 10:20 AM, Dale <rdalek1967@gmail.com> wrote:
>> Mark Knecht wrote:
>>> On Fri, Mar 2, 2012 at 3:36 AM, Dale <rdalek1967@gmail.com> wrote:
>>>> Howdy,
>>>>
>>>> I'm just wanting to make certain I don't break my rig. Info first:
>>>>
>>>> root@fireball / # eselect python list
>>>> Available Python interpreters:
>>>> [1] python2.7 *
>>>> [2] python3.1
>>>> [3] python3.2
>>>> root@fireball / #
>>>>
>>>> I ran --depclean and it wants to remove python 3.1. I ran python
>>>> updater and recompiled the needed packages. Since python 2.7 is the
>>>> default python, is it safe to remove python 3.1? As we all know, python
>>>> and portage is really good friends and portage gets real upset when it
>>>> looses its friend. I'd much rather ask this question than have to start
>>>> a thread on how to repair python with a dead portage.
>>>>
>>>> So, safe to remove? I'm thinking it is but just want the comfort of
>>>> taking someone else with me it is breaks. lol
>>>>
>>>> Dale
>>>>
>>>
>>> You should be safe but please do an
>>>
>>> eselect python list --python3
>>>
>>> and make sure you're set to 3.2 before removing 3.1.
>>>
>>> HTH,
>>> Mark
>>>
>>>
>>
>>
>> Last I heard we are not supposed to set python to 3 anything. Has that
>> changed?
>>
>> Dale
>>
>
> No, we're not supposed to set the *system* *default* to python3 yet.
> Still, if you have multiple 3.x versions installed you would want to
> set the python3 setting to the python version you want to default to
> should some program absolutely require python3, so we've got 3 real
> settings:
>
> System default - still python-2.x
> Python2 - same python-2.x version as the system default
> Python3 - what ever version you want for programs requiring Python3
>
> HTH,
> Mark
>
>


But if I tell eselect to set it to 3 something then that is what the
system will try to use right? Isn't that what eselect does? I'm
recalling what was posted after you emerge python here. The einfo/ewarn
thingy.

Again, this may have changed but what I'm wondering is if we need the
python 2 stuff any more if we can set this to python 3. After all,
python 2 has to die eventually. ^_^

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

On 2012-03-02 2:24 PM, Dale <rdalek1967@gmail.com> wrote:

But if I tell eselect to set it to 3 something then that is what the
system will try to use right? Isn't that what eselect does? I'm
recalling what was posted after you emerge python here. The einfo/ewarn
thingy.

Again, this may have changed but what I'm wondering is if we need the
python 2 stuff any more if we can set this to python 3. After all,
python 2 has to die eventually. ^_^


did you miss my earlier reply?

Mine also shows it is set to 3.1...

# eselect python list --python3
Available Python 3 interpreters:
[1] python3.1 *
[2] python3.2
myhost : Fri Mar 02, 13:07:51 : ~
#

So, that I'm guessing the correct way to do this is:

eselect python set --python3 2

?