[issue4601] permissions errors with altinstall in 3.0

STINNER Victor <[EMAIL PROTECTED]> added the comment: With Python trunk, the directory has the right permission (drwxr-xr-x) whereas build/lib.linux(...) has permission drwx--. But the problem is still open for listed files (.pyc, .pyo, .picle, .egg-info). ___

[issue4601] permissions errors with altinstall in 3.0

STINNER Victor <[EMAIL PROTECTED]> added the comment: install() method of the install_lib command (Lib/distutils/command/install_lib.py) calls self.copy_tree() which calls copy_tree() from Lib/distutils/dir_util.py. By default, this function preserve the modes (perserve_mode=1 by default). Or

[issue4601] permissions errors with altinstall in 3.0

STINNER Victor <[EMAIL PROTECTED]> added the comment: I'm able to reproduce the bug with umask set to 0027: drwxr-x--- 2 root root 3072 déc 8 22:59 (...)/lib/python3.1/lib-dynload With umask 0077, it's: drwx-- 2 root root 3072 déc 8 22:59 (...)/lib/python3.1/lib-dynload The problem is s

[issue4601] permissions errors with altinstall in 3.0

Leger <[EMAIL PROTECTED]> added the comment: My root umask = 0027 (hardened system), so the altinstall/install script don't manage umask parameter. ___ Python tracker <[EMAIL PROTECTED]> __

[issue4601] permissions errors with altinstall in 3.0

New submission from Leger <[EMAIL PROTECTED]>: Under Debian/Lenny, with Python3.0.final install from the tarball, any user can't import lib-dynload, launch IDLE ... but local root can do them. When I login in root and run "chmod -R o+rx /usr/lib/python3.0/*", users can use normaly python3.0. In