On 2011-05-10, Mick <michaelkintz...@gmail.com> wrote: >> Apparently so. It seems like it ought to pay attention to eselect. >> If I've explicitly configured my system to use 2.6 instead of 2.7, >> removing 2.6 doesn't seem like a good thing... > > I am not sure I understand: > > If you eselect python 2.7 and run python-updater (and revdep-rebuild > just in case) I would think that you *should* have a working system.
I have a number of python libraries installed that don't have ebuilds. At one point some of them weren't compatible with 2.6. I don't know if that's still the case, but I don't have time right now to go through that exercise on three machines. So I'm sticking with python 2.6 for the time being. > Unless some particular package is hardcoded to use 2.6 things should > not really break. > > Am I wrong here? It depends on what python apps/libraries you depend on. I'm sure everything that was installed via emerge would be OK. -- Grant
