KH (Mon, 28 Mar 2011 15:22:55 +0200): > I do have python-2.7 and python-3.1 emerged. I just took al look in > /usr/lib64/ and I can find trace of python2.4 python2.5 python2.6 > python2.7 python3.1 . Are those folders (2.4; 2.5; 2.6) needed anymore? > If no, why are the still there?
Is there anything else inside those dirs besides *.pyc and *.pyo files? If not, it's safe to remove them. *.py[co] are pre-semi-compiled python programs that python creates upon the first run of a *.py source. Some 1-2 years ago (and before) portage couldn't handle these remnants, as they didn't actually belong to any package. So if you had unmerged a package containing a python program which had been run at least once before the unmerge, the *.py[co] files were left in otherwise empty directories. Python-2.4 and 2.5 may fall into this period of history. 2.6 is odd. If the directories contain something more than *.py[co], the story is different. If there are no files that belong to any package, I believe it's safe to remove them. If something in there does belong to an installed package, a re-emerge should solve the problem. If you need an elegant way of sorting out the chaff, refer to a recent thread on this mailinglist - "How can I find all "orphaned" files?". -rz
