[issue15890] lib2to3 pickles created with wrong permissions

2021-10-20 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed superseder: -> Close 2to3 issues and list them here ___ Python tracker ___

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Tomi Pieviläinen
Tomi Pieviläinen added the comment: > Tomi, do you find a different behavior in 3.2? No, the behaviour is the same in 2.6-3.2: no compiled files have permissions for other than root, and all non-compiled files do (because install is run with "-m 644"). What made me report this bug was that 3.3

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Martin v . Löwis
Martin v. Löwis added the comment: It appears that it is tradition of (BSD) install(1) to ignore umask. For consistency, all installed files should get the same ACL (+-x where necessary). So I think this behavior is a bug (although apparently not a regression). --

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread R. David Murray
R. David Murray added the comment: It occurs to me that ignoring the user's selected umask could be considered a bug by some people. A package manager for a distribution should presumably ensure the correct umask during install, but if a user is doing a direct install, it seems reasonable to

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Ned Deily
Ned Deily added the comment: BTW, AFAICT, you'll get exactly the same behavior (with distribute failing due to pickle write permission) with earlier releases, like 3.2.3, if you happen to do a "make install" with an inappropriate umask value. So it appears that setting umask properly has been

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Ned Deily
Ned Deily added the comment: AFAIK, the pickles are created with exactly the same permissions as the cached pyc and pyo files have been all along. So, if you propose to change the permissions for the pickles, the compileall steps should be changed as well. --

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever, ned.deily versions: +Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Martin v . Löwis
Martin v. Löwis added the comment: I propose to postpone the fix for that to 3.3.1. Meanwhile, users should either set umask to 022 before installing, or chmod the files afterwards. -- nosy: +loewis ___ Python tracker

[issue15890] lib2to3 pickles created with wrong permissions

2012-09-09 Thread Tomi Pieviläinen
New submission from Tomi Pieviläinen: The fix of #15822 caused another break. After installing 3.3rc2 from source, ls -ltc --full-time /usr/local/lib/python3.3/lib2to3/ shows: -rw---. 1 root root 1455 2012-09-09 20:55:36.475519602 +0300 PatternGrammar3.3.0.candidate.2.pickle -rw---. 1