Opened 7 years ago

Closed 7 years ago

#5343 closed (fixed)

Settings module passed through the command line (using --settings) is being ignored

Reported by: Manoj Govindan <egmanoj@…> Owned by: adrian
Component: Core (Other) Version: master
Severity: Keywords:
Cc: egmanoj@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Consider the following command:

[django_project_dir]/> python test --settings=custom_settings

custom_settings is present in the same directory as However the settings present in custom_settings are ignored. It seems that changeset 6047 introduced changes wherein settings get configured *before* custom settings are activated.

Attachments (2) (577 bytes) - added by Manoj Govindan <egmanoj@…> 7 years ago. (410 bytes) - added by Manoj Govindan <egmanoj@…> 7 years ago.
Corrected diff.

Download all attachments as: .zip

Change History (4)

Changed 7 years ago by Manoj Govindan <egmanoj@…>

Changed 7 years ago by Manoj Govindan <egmanoj@…>

Corrected diff.

comment:1 Changed 7 years ago by russellm

(In [6050]) Refs #5343 -- Reverted [6047]. Loading custom commands was causing the settings file to get read before the options could be processed to determine if a --settings option was present. Back to the drawing board (again)...

comment:2 Changed 7 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to fixed
  • Status changed from new to closed

[6050] fixed the problem

Add Comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.