Django

Code

Ticket #5343 (closed: fixed)

Opened 1 year ago

Last modified 1 year ago

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

Reported by: Manoj Govindan <egmanoj@gmail.com> Assigned to: adrian
Milestone: Component: Core framework
Version: SVN Keywords:
Cc: egmanoj@gmail.com Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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

core.management.__init__.py.diff (0.6 kB) - added by Manoj Govindan <egmanoj@gmail.com> on 09/05/07 05:42:11.
core.management.__init__.py.2.diff (410 bytes) - added by Manoj Govindan <egmanoj@gmail.com> on 09/05/07 05:44:00.
Corrected diff.

Change History

09/05/07 05:42:11 changed by Manoj Govindan <egmanoj@gmail.com>

  • attachment core.management.__init__.py.diff added.

09/05/07 05:44:00 changed by Manoj Govindan <egmanoj@gmail.com>

  • attachment core.management.__init__.py.2.diff added.

Corrected diff.

09/05/07 09:01:31 changed 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)...

09/06/07 18:50:06 changed by russellm

  • status changed from new to closed.
  • needs_better_patch changed.
  • resolution set to fixed.
  • needs_tests changed.
  • needs_docs changed.

[6050] fixed the problem

Add/Change #5343 (Settings module passed through the command line (using --settings) is being ignored)




Change Properties
Action