1 |
Roman Zilka wrote: |
2 |
> Mark Knecht (Fri, 25 Mar 2011 06:56:20 -0700): |
3 |
> |
4 |
>> On Fri, Mar 25, 2011 at 2:50 AM, Neil Bothwick<neil@××××××××××.uk> wrote: |
5 |
>> |
6 |
>>> On Fri, 25 Mar 2011 04:37:15 -0500, Dale wrote: |
7 |
>>> |
8 |
>>> |
9 |
>>>> Out of curiosity, how long you, or someone else, been using python |
10 |
>>>> 2.7? |
11 |
>>>> |
12 |
>>> I install 2.7 on August 10th and removed 2.6 on October 5th. |
13 |
>>> |
14 |
>>> |
15 |
>>> -- |
16 |
>>> Neil Bothwick |
17 |
>>> |
18 |
>> Do you recollect whether you ran python-updater immediately after the |
19 |
>> 2.7 emerge, and do you remember whether you set 2.7 as your active |
20 |
>> version 2 python version before or after running python-updater? |
21 |
>> |
22 |
> |
23 |
> My grain of salt of experience from yesterday: |
24 |
> 1. emerged python 2.7 (upon a regular daily update) |
25 |
> 2. eselect switch to 2.7 |
26 |
> 3. python-updater (rebuilt about 30 pkgs; all went fine, except pygtk |
27 |
> complained about something apparently minor) |
28 |
> 4. re-emerge pygtk, just to be sure, this time it doesn't complain |
29 |
> 5. unmerge 2.6 |
30 |
> 6. there are no traces to be found of python 2.6; everything works |
31 |
> |
32 |
> FWIW, it went fine even on an x86 system, where python-2.7.1-r1 is still |
33 |
> ~arch. |
34 |
> |
35 |
> -rz |
36 |
> |
37 |
> |
38 |
|
39 |
I'm in the process of doing this too. So far, so good. 30 out of 53 done. |
40 |
|
41 |
Dale |
42 |
|
43 |
:-) :-) |