| 1 |
>> > One of my machines just saw a python-2.7 update and the ebuild was |
| 2 |
>> > good enough to remind me to run python-updater, but it didn't suggest |
| 3 |
>> > that I run eselect python and set the active version to 2.7. |
| 4 |
>> > |
| 5 |
>> > Should this new version python be selected first as the active python |
| 6 |
>> > 2 version and then run python-updater? |
| 7 |
>> > |
| 8 |
>> > Thanks, |
| 9 |
>> > Mark |
| 10 |
>> |
| 11 |
>> And if we should set python to 2.7, should we remove python-2.6? I |
| 12 |
>> don't think we want to break something, portage in particular. ;-) |
| 13 |
>> |
| 14 |
>> Dale |
| 15 |
>> |
| 16 |
>> :-) :-) |
| 17 |
> |
| 18 |
> I think wicd rely on python 2.6 currently. This is my setup on my laptop ! |
| 19 |
> (trying other version break networking with wicd). |
| 20 |
|
| 21 |
It looks like the latest wicd in portage supports python-2.7: |
| 22 |
|
| 23 |
http://bugs.gentoo.org/333001 |
| 24 |
|
| 25 |
- Grant |
Archives