#9714: Bug in manage.py --settings=mysettings
------------------------------------+---------------------------------------
Reporter: fero | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: | Keywords: management
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by fero):
I investigate more and exporting the DJANGO_SETTINGS_MODULE variable does
not raise an exception,
but does not work either (it is a fake :) )
mysettings.py file does not work if it is
{{{
import settings
DATABASE_USER = 'postgres' # Superuser role for the db backend of choice
}}}
however I noticed that I succeed in make it working if the file is
{{{
import settings
DATABASE_ENGINE = 'postgresql_psycopg2'
DATABASE_NAME = 'mydb'
DATABASE_USER = 'postgres' # Superuser role for the db backend of choice
}}}
It is a bit weird. Now I have no time to find the bug in django code.
It is a really strange behaviour.
--
Ticket URL: <http://code.djangoproject.com/ticket/9714#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
