On Sat, Jan 24, 2015 at 6:48 AM, Rick Johnson <rantingrickjohn...@gmail.com> wrote: > On Thursday, January 22, 2015 at 10:04:29 PM UTC-6, Chris Angelico wrote: > >> It's worth pointing out, too, that the idea isn't >> panaceaic - it's just another tool in the box. Any time >> you break related things into separate places, especially >> separate files, the tendency for them to get out of sync >> grows dramatically. > > I wonder how that "poor python interpreter" keeps all those > .pyc and .pyo files in sync with constantly changing source > code? It should be tantamount to torture! Will someone > *PLEASE* start a charity site titled: "Python's sanity fund"?
That's where one is directly derived from the other. Edit the .py file, rebuild the .pyc from it. Any dumb machine can do that... as long as timestamps can be relied on, the hard drive is correctly retaining data, etc, etc, etc. And guess what? Python isn't perfect at it. I had a bizarre problem a while ago that came down to an incorrect .pyc file in the stdlib. (I still have no idea how that came to be incorrect. The hard drive doesn't seem to be failing, and the corruption in the file looks more like a software bug than a hardware issue.) ChrisA -- https://mail.python.org/mailman/listinfo/python-list
