| 1 |
On Fri, 26 Mar 2010 16:28:29 +0000, Alec Warner <antarus@g.o> |
| 2 |
wrote: |
| 3 |
> On Fri, Mar 26, 2010 at 4:08 PM, Dale <rdalek1967@×××××.com> wrote: |
| 4 |
|
| 5 |
>> As a user, I still think this could turn into a real mess. I think |
| 6 |
there |
| 7 |
>> will be quite a few that will see python being updated, run |
| 8 |
python-updater |
| 9 |
>> and switch it to the new python. At that point, it is going to hit the |
| 10 |
fan. |
| 11 |
>> I know because this is what I always do. News item or not, when |
| 12 |
python |
| 13 |
>> gets updated, I run python-updater and make sure it is selected. |
| 14 |
> |
| 15 |
> My assumption here is that eselect-python will not let you select v3 |
| 16 |
> as your python version without some prodding (eg setting stupid |
| 17 |
> environment variables or similar.) |
| 18 |
|
| 19 |
Alec, don't assume ;) |
| 20 |
|
| 21 |
* Messages for package dev-lang/python-3.1.2: |
| 22 |
|
| 23 |
* |
| 24 |
* WARNING! |
| 25 |
* Many Python modules haven't been ported yet to Python 3.*. |
| 26 |
* Python 3 hasn't been activated and Python wrapper is still configured |
| 27 |
to use Python 2. |
| 28 |
* You can manually activate Python 3.1 using `eselect python set |
| 29 |
python3.1`. |
| 30 |
* It is recommended to currently have Python wrapper configured to use |
| 31 |
Python 2. |
| 32 |
* Having Python wrapper configured to use Python 3 is unsupported. |
| 33 |
|
| 34 |
%% sudo eselect python set python3.1 |
| 35 |
%% python --version |
| 36 |
Python 3.1.2 |
| 37 |
|
| 38 |
-Jeremy |
Archives