Message88112
| Author |
phd |
| Recipients |
phd |
| Date |
2009年05月20日.10:58:47 |
| SpamBayes Score |
1.1960025e-08 |
| Marked as misclassified |
No |
| Message-id |
<1242817129.44.0.860392010944.issue6070@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年05月20日 10:58:49 | phd | set | recipients:
+ phd |
| 2009年05月20日 10:58:49 | phd | set | messageid: <1242817129.44.0.860392010944.issue6070@psf.upfronthosting.co.za> |
| 2009年05月20日 10:58:48 | phd | link | issue6070 messages |
| 2009年05月20日 10:58:47 | phd | create |
|