-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
open_file(…, 'w', atomic=True) sets or resets permissions to 600, ignoring umask #1376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
Could you please tell me the operating system you working with?? |
andersk
added a commit
to andersk/click
that referenced
this issue
Sep 19, 2019
Fixes pallets#1376. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
andersk
added a commit
to andersk/click
that referenced
this issue
Sep 19, 2019
Fixes pallets#1376. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
andersk
added a commit
to andersk/click
that referenced
this issue
Sep 19, 2019
Fixes pallets#1376. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
andersk
added a commit
to andersk/click
that referenced
this issue
Oct 3, 2019
Fixes pallets#1376. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
I'm running OS X, the problem also occurs on Debian |
davidism
pushed a commit
to andersk/click
that referenced
this issue
Feb 17, 2020
Fixes pallets#1376. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Files are normally created with permission
666 & umask
as expected:However, opening a new or existing file with
atomic=True
sets or resets its permissions to600
unconditionally:I’d expect a new file created with
atomic=True
to be created with the usual permission666 & umask
, and an existing file opened withatomic=True
to have the previous permissions preserved. (There’s probably no way to preserve permissions atomically; taking the previous permissions at the time of the initial open is fine.)The text was updated successfully, but these errors were encountered: