Mark Knecht wrote:
> Dale,
>I'll try to make it clearer:
>
> The command "eselect python set #" sets the system python profile.
> This command allows you to choose any python currently on your system.
> You should only choose a python2 setting at this time.
>
> The commands:
> eselect python
On Fri, Mar 2, 2012 at 11:24 AM, Dale wrote:
> Mark Knecht wrote:
>> On Fri, Mar 2, 2012 at 10:20 AM, Dale wrote:
>>> Mark Knecht wrote:
On Fri, Mar 2, 2012 at 3:36 AM, Dale wrote:
> Howdy,
>
> I'm just wanting to make certain I don't break my rig. Info first:
>
> root@
On 2012-03-02 2:24 PM, Dale 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 wo
Mark Knecht wrote:
> On Fri, Mar 2, 2012 at 10:20 AM, Dale wrote:
>> Mark Knecht wrote:
>>> On Fri, Mar 2, 2012 at 3:36 AM, 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 i
On Fri, Mar 2, 2012 at 10:20 AM, Dale wrote:
> Mark Knecht wrote:
>> On Fri, Mar 2, 2012 at 3:36 AM, 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] pytho
Mark Knecht wrote:
> On Fri, Mar 2, 2012 at 3:36 AM, 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@f
On 2012-03-02 9:28 AM, Mark Knecht 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:
On Fri, Mar 2, 2012 at 3:36 AM, 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 --depclea
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 t
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
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 py
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
12 matches
Mail list logo
