Code

Opened 7 years ago

Closed 7 years ago

#4688 closed (fixed)

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

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

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@… 7 years ago.
Patch to check and fix permissions on settings.py if necessary

Download all attachments as: .zip

Change History (2)

Changed 7 years ago by tstromberg@…

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

comment:1 Changed 7 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

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

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.