Hi Mark
On 10/20/2009 02:37 PM, Mark Perew wrote:
rpm -V python
S.5....T. /usr/lib/python2.6/subprocess.pyc
Yeah. I'm a little confused by that. So, I checked the date:
ll /usr/lib/python2.6/sub*
-rw-r--r--. 1 root root 45471 2009-06-08 16:07
/usr/lib/python2.6/subprocess.py
-rw-r--r--. 1 root root 119 2009-08-26 21:15
/usr/lib/python2.6/subprocess.pyc
-rw-r--r--. 1 root root 32985 2009-06-08 16:07
/usr/lib/python2.6/subprocess.pyo
I am baffled as to what would have caused the module to recompile on 8/26.
Hmm, yeah, that indeed is weird. Note that since the file size is way too small
(smaller than the /optimized/ .pyo), i doubt it is even a recompiled file. You
may want to either run a rpm -Va or check the filesystem for all files modified
on that date (ref, find -mtime), if you really are curious.
If you care only about making yum work, you can of course delete the .pyc, which
would cause yum (or any other python script that uses subprocess.py) to recreate
it the next time subprocess is imported ...tho' you probably knew that already.
cheers,
- steve
--
random non tech spiel: http://lonetwin.blogspot.com/
tech randomness: http://lonehacks.blogspot.com/
what i'm stumbling into: http://lonetwin.stumbleupon.com/
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
