#9714: Bug in manage.py --settings=mysettings
------------------------------------+---------------------------------------
Reporter: fero | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: invalid | Keywords: management
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => invalid
Comment:
There is no Django bug here. All settings variables must be in the module-
level namespace of the settings file. In other words, Django looks for the
all-capitals variables in the file you say is the settings file. So in
your first case, there is not settings called DATABASE_USER. There is
something in the `settings` namespace -- `settings.DATABASE_USER`, but you
have told Django that the `mysettings` file contains all the settings, so
it is look for `mysettings.DATABASE_USER`, in effect.
That is why every example that shows importing from one settings file into
another uses `from settings import *`.
--
Ticket URL: <http://code.djangoproject.com/ticket/9714#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
