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 vstinner
Recipients brett.cannon, christian.heimes, serhiy.storchaka, socketpair, vstinner
Date 2017-01-10.21:11:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwb7z0MQTPtVs=FbD3rHHqh5UYBj+jh95u=FPuQBous2xQ@mail.gmail.com>
In-reply-to <1484074872.13.0.30275711389.issue29214@psf.upfronthosting.co.za>
Content
I don't understand the problem with umask(). It's standard and affect all
code even C extension calling directly or indirectly open(). It is more
secure to use umask() than setting mode on a few Python open() calls no?

For example, Python creates .pyc files. You cannot (easily) modify the
open() call to set mode, whereas it is affected by umask().

If you call umask() at startup, it affects all threads, there is no race
condition like open()+fchmod().
History
Date User Action Args
2017-01-10 21:11:59vstinnersetrecipients: + vstinner, brett.cannon, christian.heimes, socketpair, serhiy.storchaka
2017-01-10 21:11:59vstinnerlinkissue29214 messages
2017-01-10 21:11:59vstinnercreate