> -----Original Message----- > From: Paul F Dubois > > On a 384 processor job we have once again encountered that old question of > corrupted .pyc files, sometimes resulting in an error, sometimes > in a silent > wrong behavior later. I know this was allegedly fixed previously but it > looks like it doesn't really work. We lost a couple of weeks work > this time. > > Didn't we talk about an option to not make pyc files? I can't seem to find > it. (We totally don't care about the cost of imports. The documentation > mentions "ihooks" but not the module itself. I know that > importing has been > an area of create turmoil so I don't really know where to look.) > I couldn't > even find the list of command-line options for Python itself except a > mention of -c in the tutorial. Any pointers would be appreciated. I hadn't considered the option of not making .pyc files, though I've complained about .pyo files in the past with distutils, but now compilation is optional there. The .pyc and .pyo files certainly clutter a directory. If there is no significant performance improvement for loading and using .pyc files or the difference is only significant for large files or certain code constructs, maybe they shouldn't be automatically created. I guess this is another area for test cases. ka
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4