On 2010-06-09 11:08 AM, Dale wrote: > If I recall correctly, there are a few programs that can run with > python 3. Thing is, there are still a LOT of them that can't run with > it and must have python 2. If you switch to python 3, you will have a > mess on your hands. If nothing actually requires python 3, mask it > for now. It will be a while before you will have to have it anyway. > When that time comes, portage will tell you that some package that > must have python 3 only is masked. Then you can remove the mask, > install it and switch to it. > > This is just to save you some "issues" later on. Trying to use python > 3 right now is not going to work. Wait until things are able to use > and go through the update process then and only have to do it once. > > That's my $0.02 worth.
So... for those of use who have already installed it (and thankfully I did actually read the notes about not switching to it), should me uninstall it then mask it? Or just leave it alone? I'm guessing it won't hurt anything, again as long as I don't stupidly switch to it?
