New submission from Oleg Broytmann <p...@phd.pp.ru>: On compilation of .pyc/.pyo bytecode files on import Python 2.6 copies Unix file access attributes (-rwx-) from the imported file. I'd think it's ok except for executable (-x-) bit - bytecode files are not directly executable. That is, for a module.py with attributes -rwxr-x--- I expect python2.6 -c 'import module' would produce module.pyc with attributes -rw-r-----.
python compileall.py . saves compiled files without the executable bit; it doesn't copy attributes - it just saves files and saving obeys umask. python2.5 -c 'import module.py' doesn't copy the executable bit, it obeys umask too. I consider this as a regression in 2.6. Please mask out executable bits on bytecode files saving. ---------- components: Interpreter Core messages: 88112 nosy: phd severity: normal status: open title: Pyhon 2.6 makes .pyc/.pyo bytecode files executable type: behavior versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6070> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
