Mike Kazantsev wrote: > On Mon, 08 Jun 2009 19:27:39 -0500 > Dale <rdalek1...@gmail.com> wrote: > > >>> Also, be careful when you parse the output of the command. Most of the >>> .pyc and .pyo files in the python2.5 directories are byte-compiled >>> version that python generated dynamically the first time they are >>> used. For example: ..../Numeric/numeric_version.py was installed by >>> the ebuild and thuse qfile tells me it belongs to dev-python/numeric, >>> but .../Numeric/numeric_version.pyc is listed as an "orphan". While it >>> is safe to delete, it will just be regenerated again later, wasting >>> computing cycles. >>> >> That's sort of what I was thinking. It was generated when it was >> started up the first time. I also noticed some things that I installed >> in the Seamonkey directory too. Adblock was one of those. >> > > That's not quite correct: .py[co] are generated by emerge right after > package installaton and these won't come back unless you use these libs > as root, since python won't have write access to these paths and will > be byte-compiling each script on-the-fly. > >
All the more reason for me to leave them alone then huh? ;-) We all know what happens to portage when python pukes up last weeks meal. :/ Dale :-) :-)
