Opened 18 years ago

Closed 17 years ago

#4688 closed (fixed)

startproject breaks if django files are read-only (settings.py)

Reported by: tstromberg@… Owned by: Adrian Holovaty
Component: Core (Management commands) Version: dev
Severity: Keywords: settings.py read-only
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

We keep all of our dependencies, including Django, in a local revision control repository. In our system, all files are stored read-only unless you have them checked out for edit. Django startproject makes a copy of settings.py and adds a secret key to it, but does not check to see if settings.py is writeable beforehand. I've attached a patch that we will be using in our internal copy of Django, which is against an SVN checkout from today.

Attachments (1)

django-core-management.patch​ (850 bytes ) - added by tstromberg@… 18 years ago.
Patch to check and fix permissions on settings.py if necessary

Download all attachments as: .zip

Change History (2)

by tstromberg@…, 18 years ago

Attachment: django-core-management.patch​ added

Patch to check and fix permissions on settings.py if necessary

comment:1 by Adrian Holovaty, 17 years ago

Resolution: → fixed
Status: new → closed

(In [5593]) Fixed #4688 -- startproject no longer breaks when Django files are read-only. Thanks, tstromberg@… and Google guys

Note: See TracTickets for help on using tickets.
Back to Top