#31821 closed Cleanup/optimization (fixed)
FILE_UPLOAD_PERMISSIONS docs contain outdated note.
| Reported by: | Pavel Mises | Owned by: | Harpreet Sharma |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | FILE_UPLOAD_PERMISSIONS |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
The current documentation for FILE_UPLOAD_PERMISSIONS (https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-FILE_UPLOAD_PERMISSIONS) states two contradicting pieces of information:
- The default value of
FILE_UPLOAD_PERMISSIONSis0o644. - If this isn’t given or is None, you’ll get operating-system dependent behavior.
It seems that after changing the default value in #30004, the part stating "this isn’t given" is no longer valid and should be removed.
Change History (6)
comment:1 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 4 years ago
| Summary: | Confusing documentation for FILE_UPLOAD_PERMISSIONS → FILE_UPLOAD_PERMISSIONS docs contain outdated note. |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Type: | Bug → Cleanup/optimization |
comment:3 by , 4 years ago
| Has patch: | set |
|---|
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/13231