Brett Cannon <br...@python.org> added the comment: Turns out the failure is because I have simply been opening bytecode files for writing using _io.FileIO(..., 'w') which just uses the OS's default permissions. Guess that won't cut it anymore. =)
So does this mean I am expected to chmod the bytecode file to have matching read and write bits to the source but no execution bits regardless of the source file? And what about writing new bytecode files? I am not about to ignore permissions and simply write over files just because I can as someone could have set them independently of Python to be read-only. Let me know that I am doing the right thing, David. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6526> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
