homepage

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 tpievila
Recipients Arfrever, loewis, ned.deily, r.david.murray, tpievila
Date 2012年09月10日.06:23:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347258181.67.0.722926318399.issue15890@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.3rc1 does not have this behaviour: while the pickles had a bad timestamp, the permissions were just fine, so I assumed that someone had changed the this intentionally.
Also this hasn't been a problem in Python2.x. I can install 2.6.8 and 2.7.3 from source without fixing any permissions, and still have a working Python installation. 3.2.3 requires chmoding the lib2to3 pickles, but no other compiled files need to be touched (it seems that they aren't really needed).
History
Date User Action Args
2012年09月10日 06:23:01tpievilasetrecipients: + tpievila, loewis, ned.deily, Arfrever, r.david.murray
2012年09月10日 06:23:01tpievilasetmessageid: <1347258181.67.0.722926318399.issue15890@psf.upfronthosting.co.za>
2012年09月10日 06:23:01tpievilalinkissue15890 messages
2012年09月10日 06:23:00tpievilacreate

AltStyle によって変換されたページ (->オリジナル) /