Opened 17 years ago

Closed 17 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 Holovaty
Component: Core (Other) Version: dev
Severity: Keywords:
Cc: egmanoj@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Consider the following command:

[django_project_dir]/> python manage.py test --settings=custom_settings

custom_settings is present in the same directory as settings.py. 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)

core.management.__init__.py.diff​ (577 bytes ) - added by Manoj Govindan <egmanoj@…> 17 years ago.
core.management.__init__.py.2.diff​ (410 bytes ) - added by Manoj Govindan <egmanoj@…> 17 years ago.
Corrected diff.

Download all attachments as: .zip

Change History (4)

by Manoj Govindan <egmanoj@…>, 17 years ago

Attachment: core.management.__init__.py.diff​ added

by Manoj Govindan <egmanoj@…>, 17 years ago

Attachment: core.management.__init__.py.2.diff​ added

Corrected diff.

comment:1 by Russell Keith-Magee, 17 years ago

(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 by Russell Keith-Magee, 17 years ago

Resolution: → fixed
Status: new → closed

[6050] fixed the problem

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