This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author phd
Recipients phd
Date 2009-05-20.10:58:47
SpamBayes Score 1.196e-08
Marked as misclassified No
Message-id <>
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 with attributes -rwxr-x---
I expect python2.6 -c 'import module' would produce module.pyc with
attributes -rw-r-----.

python . saves compiled files without the executable bit;
it doesn't copy attributes - it just saves files and saving obeys umask.
python2.5 -c 'import' 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.
Date User Action Args
2009-05-20 10:58:49phdsetrecipients: + phd
2009-05-20 10:58:49phdsetmessageid: <>
2009-05-20 10:58:48phdlinkissue6070 messages
2009-05-20 10:58:47phdcreate