Re: Django Improper Configuration

[Mark Penix]

your whole engine line should read
'ENGINE': 'django.db.backends.sqlite3'

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

it still doesn't work. I typed it like you've suggested and it keeps saying
that the database ENGINE has not been set.

On Sun, Jan 23, 2011 at 5:11 AM, Mark Penix  wrote:

> your whole engine line should read
> 'ENGINE': 'django.db.backends.sqlite3'
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Karen Tracey]

On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:

> it still doesn't work. I typed it like you've suggested and it keeps saying
> that the database ENGINE has not been set.
>
>
If you are using ENGINE by itself, you need to be using Django 1.2 or higher
and ENGINE is a key in the dictionary of settings for the default database,
not a single ENGINE line in settings.py. See:

http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases

for details.

If you are using a Django version prior to 1.2, the setting you should be
using is DATABASE_ENGINE (see
http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not
just ENGINE.

Karen
-- 
http://tracey.org/kmt/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

I've used the tutorials and it doesn't work. I've done exactly what the
tutorial says, and it keeps saying that the ENGINE has not been set in the
setting. I am also using Django 1.2 or higher version.

On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:

> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:
>
>> it still doesn't work. I typed it like you've suggested and it keeps
>> saying that the database ENGINE has not been set.
>>
>>
> If you are using ENGINE by itself, you need to be using Django 1.2 or
> higher and ENGINE is a key in the dictionary of settings for the default
> database, not a single ENGINE line in settings.py. See:
>
> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>
> for details.
>
> If you are using a Django version prior to 1.2, the setting you should be
> using is DATABASE_ENGINE (see
> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not
> just ENGINE.
>
> Karen
> --
> http://tracey.org/kmt/
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

Rather than have us guess what is in your settings file, post that whole 
section. For example:

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2', 
'postgresql', 'mysql', 'sqlite3' or 'oracle'.
'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'), 
 # Or path to database file if using sqlite3.
'USER': '',  # Not used with sqlite3.
'PASSWORD': '',  # Not used with sqlite3.
'HOST': '',  # Set to empty string for 
localhost. Not used with sqlite3.
'PORT': '',  # Set to empty string for default. 
Not used with sqlite3.
}
}

This will allow everyone to see if you have mucked up some other part of the 
settings.

Graham

On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>
> I've used the tutorials and it doesn't work. I've done exactly what the 
> tutorial says, and it keeps saying that the ENGINE has not been set in the 
> setting. I am also using Django 1.2 or higher version.
>
> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:
>
>> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:
>>
>>> it still doesn't work. I typed it like you've suggested and it keeps 
>>> saying that the database ENGINE has not been set.
>>>
>>>
>> If you are using ENGINE by itself, you need to be using Django 1.2 or 
>> higher and ENGINE is a key in the dictionary of settings for the default 
>> database, not a single ENGINE line in settings.py. See: 
>>
>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>
>> for details. 
>>
>> If you are using a Django version prior to 1.2, the setting you should be 
>> using is DATABASE_ENGINE (see 
>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not 
>> just ENGINE.
>>
>> Karen
>> -- 
>> http://tracey.org/kmt/
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To post to this group, send email to django...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

Sorry about that... here is what I have in the settings.py ( similiar to
what you showed, but mine is abit different in the NAME section):

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
'postgresql', 'mysql', 'sqlite3' or 'oracle'.
'NAME':  'home/username/directory/database'  # Or
path to database file if using sqlite3.
'USER': '',  # Not used with sqlite3.
'PASSWORD': '',  # Not used with sqlite3.
'HOST': '',  # Set to empty string for
localhost. Not used with sqlite3.
'PORT': '',  # Set to empty string for default.
Not used with sqlite3.
}
}

Inside the settings.py file, in the template_dirs section, there's a line
says os.path.join(os.path.dirname(_file_), 'templates')

If I comment that, then there's a error saying it doesn't recognize _file_.
I commented that line, then it says that the setting ENGINE has not been
set.


On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

> Rather than have us guess what is in your settings file, post that whole
> section. For example:
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add
> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),
># Or path to database file if using sqlite3.
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for default.
> Not used with sqlite3.
> }
> }
>
> This will allow everyone to see if you have mucked up some other part of
> the settings.
>
> Graham
>
> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>
>> I've used the tutorials and it doesn't work. I've done exactly what the
>> tutorial says, and it keeps saying that the ENGINE has not been set in the
>> setting. I am also using Django 1.2 or higher version.
>>
>> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:
>>
>>> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:
>>>
 it still doesn't work. I typed it like you've suggested and it keeps
 saying that the database ENGINE has not been set.


>>> If you are using ENGINE by itself, you need to be using Django 1.2 or
>>> higher and ENGINE is a key in the dictionary of settings for the default
>>> database, not a single ENGINE line in settings.py. See:
>>>
>>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>>
>>> for details.
>>>
>>> If you are using a Django version prior to 1.2, the setting you should be
>>> using is DATABASE_ENGINE (see
>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not
>>> just ENGINE.
>>>
>>> Karen
>>> --
>>> http://tracey.org/kmt/
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>
> Sorry about that... here is what I have in the settings.py ( similiar to 
> what you showed, but mine is abit different in the NAME section):
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 
> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME':  'home/username/directory/database'  # Or 
> path to database file if using sqlite3.
>

You deleted the comma after the string and missing leading slash on path. 
Try:

'NAME':  '/home/username/directory/database',  # Or 
path to database file if using sqlite3.

Not sure how you didn't just get a syntax error.

Graham
 

> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for 
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for default. 
> Not used with sqlite3.
> }
> }
>
> Inside the settings.py file, in the template_dirs section, there's a line 
> says os.path.join(os.path.dirname(_file_), 'templates')
>
> If I comment that, then there's a error saying it doesn't recognize _file_. 
> I commented that line, then it says that the setting ENGINE has not been 
> set.
>
>
> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
> wrote:
>
>> Rather than have us guess what is in your settings file, post that whole 
>> section. For example:
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', # Add 
>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),   
>># Or path to database file if using sqlite3.
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for 
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for 
>> default. Not used with sqlite3.
>> }
>> }
>>
>> This will allow everyone to see if you have mucked up some other part of 
>> the settings.
>>
>> Graham
>>
>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>
>>> I've used the tutorials and it doesn't work. I've done exactly what the 
>>> tutorial says, and it keeps saying that the ENGINE has not been set in the 
>>> setting. I am also using Django 1.2 or higher version.
>>>
>>> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:
>>>
  On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:

> it still doesn't work. I typed it like you've suggested and it keeps 
> saying that the database ENGINE has not been set.
>
>
 If you are using ENGINE by itself, you need to be using Django 1.2 or 
 higher and ENGINE is a key in the dictionary of settings for the default 
 database, not a single ENGINE line in settings.py. See: 


 http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases

 for details. 

 If you are using a Django version prior to 1.2, the setting you should 
 be using is DATABASE_ENGINE (see 
 http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), 
 not just ENGINE.

 Karen
 -- 
 http://tracey.org/kmt/

  -- 
 You received this message because you are subscribed to the Google 
 Groups "Django users" group.
 To post to this group, send email to djan...@googlegroups.com.
 To unsubscribe from this group, send email to 
 django-...@googlegroups.com.

 For more options, visit this group at 
 http://groups.google.com/group/django-users?hl=en.

>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To post to this group, send email to django...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

Still doesn't work. But thank you for trying to help me. It keep giving me
the same ENGINE configuration that it is not set.

On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>>
>> Sorry about that... here is what I have in the settings.py ( similiar to
>> what you showed, but mine is abit different in the NAME section):
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME':  'home/username/directory/database'  # Or
>> path to database file if using sqlite3.
>>
>
> You deleted the comma after the string and missing leading slash on path.
> Try:
>
> 'NAME':  '/home/username/directory/database',  # Or
> path to database file if using sqlite3.
>
> Not sure how you didn't just get a syntax error.
>
> Graham
>
>
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for
>> default. Not used with sqlite3.
>> }
>> }
>>
>> Inside the settings.py file, in the template_dirs section, there's a line
>> says os.path.join(os.path.dirname(_file_), 'templates')
>>
>> If I comment that, then there's a error saying it doesn't recognize
>> _file_. I commented that line, then it says that the setting ENGINE has not
>> been set.
>>
>>
>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>> wrote:
>>
>>> Rather than have us guess what is in your settings file, post that whole
>>> section. For example:
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),
>>>  # Or path to database file if using sqlite3.
>>> 'USER': '',  # Not used with sqlite3.
>>> 'PASSWORD': '',  # Not used with sqlite3.
>>> 'HOST': '',  # Set to empty string for
>>> localhost. Not used with sqlite3.
>>> 'PORT': '',  # Set to empty string for
>>> default. Not used with sqlite3.
>>> }
>>> }
>>>
>>> This will allow everyone to see if you have mucked up some other part of
>>> the settings.
>>>
>>> Graham
>>>
>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>
 I've used the tutorials and it doesn't work. I've done exactly what the
 tutorial says, and it keeps saying that the ENGINE has not been set in the
 setting. I am also using Django 1.2 or higher version.

 On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:

>  On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:
>
>> it still doesn't work. I typed it like you've suggested and it keeps
>> saying that the database ENGINE has not been set.
>>
>>
> If you are using ENGINE by itself, you need to be using Django 1.2 or
> higher and ENGINE is a key in the dictionary of settings for the default
> database, not a single ENGINE line in settings.py. See:
>
>
> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>
> for details.
>
> If you are using a Django version prior to 1.2, the setting you should
> be using is DATABASE_ENGINE (see
> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine),
> not just ENGINE.
>
> Karen
> --
> http://tracey.org/kmt/
>
>  --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To post to this group, send email to djan...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-...@googlegroups.com.
>
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message becau

Re: Django Improper Configuration

[Graham Dumpleton]

Provide  the full error including any Python traceback so we can see where 
the error is occurring. If running manage.py runserver, easiest thing to do 
is to provide the whole output from running the command.

Graham

On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>
> Still doesn't work. But thank you for trying to help me. It keep giving me 
> the same ENGINE configuration that it is not set.
>
> On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>>>
>>> Sorry about that... here is what I have in the settings.py ( similiar to 
>>> what you showed, but mine is abit different in the NAME section):
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3', # Add 
>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>> 'NAME':  'home/username/directory/database'  # Or 
>>> path to database file if using sqlite3.
>>>
>>
>> You deleted the comma after the string and missing leading slash on path. 
>> Try:
>>
>> 'NAME':  '/home/username/directory/database',  # 
>> Or path to database file if using sqlite3.
>>
>> Not sure how you didn't just get a syntax error.
>>
>> Graham
>>  
>>
>>> 'USER': '',  # Not used with sqlite3.
>>> 'PASSWORD': '',  # Not used with sqlite3.
>>> 'HOST': '',  # Set to empty string for 
>>> localhost. Not used with sqlite3.
>>> 'PORT': '',  # Set to empty string for 
>>> default. Not used with sqlite3.
>>> }
>>> }
>>>
>>> Inside the settings.py file, in the template_dirs section, there's a line 
>>> says os.path.join(os.path.dirname(_file_), 'templates')
>>>
>>> If I comment that, then there's a error saying it doesn't recognize 
>>> _file_. I commented that line, then it says that the setting ENGINE has not 
>>> been set.
>>>
>>>
>>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton wrote:
>>>
  Rather than have us guess what is in your settings file, post that 
 whole section. For example:

 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3', # Add 
 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'), 
  # Or path to database file if using sqlite3.
 'USER': '',  # Not used with sqlite3.
 'PASSWORD': '',  # Not used with sqlite3.
 'HOST': '',  # Set to empty string for 
 localhost. Not used with sqlite3.
 'PORT': '',  # Set to empty string for 
 default. Not used with sqlite3.
 }
 }

 This will allow everyone to see if you have mucked up some other part of 
 the settings.

 Graham

 On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:

>  I've used the tutorials and it doesn't work. I've done exactly what 
> the tutorial says, and it keeps saying that the ENGINE has not been set 
> in 
> the setting. I am also using Django 1.2 or higher version.
>
> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey wrote:
>
>>  On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey 
>> wrote:
>>
>>> it still doesn't work. I typed it like you've suggested and it keeps 
>>> saying that the database ENGINE has not been set.
>>>
>>>
>> If you are using ENGINE by itself, you need to be using Django 1.2 or 
>> higher and ENGINE is a key in the dictionary of settings for the default 
>> database, not a single ENGINE line in settings.py. See: 
>>
>>
>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>
>> for details. 
>>
>> If you are using a Django version prior to 1.2, the setting you should 
>> be using is DATABASE_ENGINE (see 
>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), 
>> not just ENGINE.
>>
>> Karen
>> -- 
>> http://tracey.org/kmt/
>>
>>  -- 
>> You received this message because you are subscribed to the Google 
>> Groups "Django users" group.
>> To post to this group, send email to dja...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> djang...@googlegroups.com.
>>
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>  -- 
 You received this message because you are subscribed to the Google 
 Groups "Django users" group.
 To post to this group, send email to djan...@googlegroups.com.
 To unsubscribe from this group, send email to 
 django-...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group

Re: Django Improper Configuration

[Kimberly Harvey]

username@debian:~/wikicamps$ python manage.py runserver
Validating models
0 errors found

Django version 1.2.4, using settings 'wikicamp.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

It runs fine, but yet I faced problem with the database ENGINE.
On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

> Provide  the full error including any Python traceback so we can see where
> the error is occurring. If running manage.py runserver, easiest thing to do
> is to provide the whole output from running the command.
>
> Graham
>
> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>
>> Still doesn't work. But thank you for trying to help me. It keep giving me
>> the same ENGINE configuration that it is not set.
>>
>> On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton 
>> wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:

 Sorry about that... here is what I have in the settings.py ( similiar to
 what you showed, but mine is abit different in the NAME section):

 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3', # Add
 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
 'NAME':  'home/username/directory/database'  #
 Or path to database file if using sqlite3.

>>>
>>> You deleted the comma after the string and missing leading slash on path.
>>> Try:
>>>
>>> 'NAME':  '/home/username/directory/database',  #
>>> Or path to database file if using sqlite3.
>>>
>>> Not sure how you didn't just get a syntax error.
>>>
>>> Graham
>>>
>>>
 'USER': '',  # Not used with sqlite3.
 'PASSWORD': '',  # Not used with sqlite3.
 'HOST': '',  # Set to empty string for
 localhost. Not used with sqlite3.
 'PORT': '',  # Set to empty string for
 default. Not used with sqlite3.
 }
 }

 Inside the settings.py file, in the template_dirs section, there's a
 line says os.path.join(os.path.dirname(_file_), 'templates')

 If I comment that, then there's a error saying it doesn't recognize
 _file_. I commented that line, then it says that the setting ENGINE has not
 been set.


 On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
 wrote:

>  Rather than have us guess what is in your settings file, post that
> whole section. For example:
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add
> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),
># Or path to database file if using sqlite3.
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for
> default. Not used with sqlite3.
> }
> }
>
> This will allow everyone to see if you have mucked up some other part
> of the settings.
>
> Graham
>
> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>
>>  I've used the tutorials and it doesn't work. I've done exactly what
>> the tutorial says, and it keeps saying that the ENGINE has not been set 
>> in
>> the setting. I am also using Django 1.2 or higher version.
>>
>> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey wrote:
>>
>>>  On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey 
>>> wrote:
>>>
 it still doesn't work. I typed it like you've suggested and it keeps
 saying that the database ENGINE has not been set.


>>> If you are using ENGINE by itself, you need to be using Django 1.2 or
>>> higher and ENGINE is a key in the dictionary of settings for the default
>>> database, not a single ENGINE line in settings.py. See:
>>>
>>>
>>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>>
>>> for details.
>>>
>>> If you are using a Django version prior to 1.2, the setting you
>>> should be using is DATABASE_ENGINE (see
>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine),
>>> not just ENGINE.
>>>
>>> Karen
>>> --
>>> http://tracey.org/kmt/
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To post to this group, send email to dja...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> djang...@googlegrou

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote:
>
> username@debian:~/wikicamps$ python manage.py runserver
> Validating models
> 0 errors found
>
> Django version 1.2.4, using settings 'wikicamp.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
>
> It runs fine, but yet I faced problem with the database ENGINE. 
>

Where are you seeing that error because it isn't in what you quote above?

If it is in the browser, paste the Python exception details and traceback 
from the browser. Not everything, just the exception message and traceback 
will do.

In other words, we need to see the actual context in which the real error 
message is displayed and the exact wording of the error message and the 
location.

Graham
 

> On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton 
> wrote:
>
>> Provide  the full error including any Python traceback so we can see where 
>> the error is occurring. If running manage.py runserver, easiest thing to do 
>> is to provide the whole output from running the command.
>>
>> Graham
>>
>> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>>
>>> Still doesn't work. But thank you for trying to help me. It keep giving 
>>> me the same ENGINE configuration that it is not set.
>>>
>>> On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton wrote:
>>>


 On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>
> Sorry about that... here is what I have in the settings.py ( similiar 
> to what you showed, but mine is abit different in the NAME section):
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 
> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME':  'home/username/directory/database'  # 
> Or path to database file if using sqlite3.
>

 You deleted the comma after the string and missing leading slash on 
 path. Try:

 'NAME':  '/home/username/directory/database',  # 
 Or path to database file if using sqlite3.

 Not sure how you didn't just get a syntax error.

 Graham
  

> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for 
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for 
> default. Not used with sqlite3.
> }
> }
>
> Inside the settings.py file, in the template_dirs section, there's a 
> line says os.path.join(os.path.dirname(_file_), 'templates')
>
> If I comment that, then there's a error saying it doesn't recognize 
> _file_. I commented that line, then it says that the setting ENGINE has 
> not 
> been set.
>
>
> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
> wrote:
>
>>  Rather than have us guess what is in your settings file, post that 
>> whole section. For example:
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', # Add 
>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),   
>># Or path to database file if using sqlite3.
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for 
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for 
>> default. Not used with sqlite3.
>> }
>> }
>>
>> This will allow everyone to see if you have mucked up some other part 
>> of the settings.
>>
>> Graham
>>
>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>
>>>  I've used the tutorials and it doesn't work. I've done exactly what 
>>> the tutorial says, and it keeps saying that the ENGINE has not been set 
>>> in 
>>> the setting. I am also using Django 1.2 or higher version.
>>>
>>> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey wrote:
>>>
   On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <
 kha...@gmail.com> wrote:

> it still doesn't work. I typed it like you've suggested and it 
> keeps saying that the database ENGINE has not been set.
>
>
 If you are using ENGINE by itself, you need to be using Django 1.2 
 or higher and ENGINE is a key in the dictionary of settings for the 
 default 
 database, not a single ENGINE line in settings.py. See: 


 http://docs.djangoproject.com/en/dev/ref/s

Re: Django Improper Configuration

[Steven Elliott Jr]

I remember that the one time I tried sqlite it complained until I put a .db 
suffix on the name of my database. If you do not specify the full path and just 
specify a name, then it will just create the database file in your project's 
root directory. 

So, under name just put:

'NAME' : 'database.db',

And see if that works. 

-Steve
Sent from my iPhone 


On Jan 23, 2011, at 9:48 PM, Graham Dumpleton  
wrote:

> 
> 
> On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote:
> username@debian:~/wikicamps$ python manage.py runserver
> Validating models
> 0 errors found
> 
> Django version 1.2.4, using settings 'wikicamp.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
> 
> It runs fine, but yet I faced problem with the database ENGINE. 
> 
> Where are you seeing that error because it isn't in what you quote above?
> 
> If it is in the browser, paste the Python exception details and traceback 
> from the browser. Not everything, just the exception message and traceback 
> will do.
> 
> In other words, we need to see the actual context in which the real error 
> message is displayed and the exact wording of the error message and the 
> location.
> 
> Graham
>  
> On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton  
> wrote:
> Provide  the full error including any Python traceback so we can see where 
> the error is occurring. If running manage.py runserver, easiest thing to do 
> is to provide the whole output from running the command.
> 
> Graham
> 
> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
> Still doesn't work. But thank you for trying to help me. It keep giving me 
> the same ENGINE configuration that it is not set.
> 
> On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton  wrote:
> 
> 
> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
> Sorry about that... here is what I have in the settings.py ( similiar to what 
> you showed, but mine is abit different in the NAME section):
> 
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2', 
> 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME':  'home/username/directory/database'  # Or 
> path to database file if using sqlite3.
> 
> You deleted the comma after the string and missing leading slash on path. Try:
> 
> 'NAME':  '/home/username/directory/database',  # Or 
> path to database file if using sqlite3.
> 
> Not sure how you didn't just get a syntax error.
> 
> Graham
>  
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for localhost. 
> Not used with sqlite3.
> 'PORT': '',  # Set to empty string for default. 
> Not used with sqlite3.
> }
> }
> 
> Inside the settings.py file, in the template_dirs section, there's a line 
> says os.path.join(os.path.dirname(_file_), 'templates')
> 
> If I comment that, then there's a error saying it doesn't recognize _file_. I 
> commented that line, then it says that the setting ENGINE has not been set.
> 
> 
> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton  wrote:
> Rather than have us guess what is in your settings file, post that whole 
> section. For example:
> 
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2', 
> 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),  
> # Or path to database file if using sqlite3.
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for localhost. 
> Not used with sqlite3.
> 'PORT': '',  # Set to empty string for default. 
> Not used with sqlite3.
> }
> }
> 
> This will allow everyone to see if you have mucked up some other part of the 
> settings.
> 
> Graham
> 
> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
> I've used the tutorials and it doesn't work. I've done exactly what the 
> tutorial says, and it keeps saying that the ENGINE has not been set in the 
> setting. I am also using Django 1.2 or higher version.
> 
> On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey  wrote:
> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey  wrote:
> it still doesn't work. I typed it like you've suggested and it keeps saying 
> that the database ENGINE has not been set.
> 
> 
> If you are using ENGINE by itself, you need to be using Django 1.2 or higher 
> and ENGINE is a key in the dictionary of settings for the default database, 
> not a single ENGINE line in settings.py. See: 
> 
> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
> 
> for details. 
> 

Re: Django Improper Configuration

[Kimberly Harvey]

The error that I am seeing is in the shell/ the terminal. I am unable to
paste the exception problems on here. But I've typed it... look below

After I've ran the python manage.py runserver, there was NO errors. But when
I try to use, python manage.py syncdb, it showed errors/exceptions:

Traceback ( most recent call last):
 File "manage.py", line 11, in 
execute_manager(settings)
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
438, in execute manager
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
379, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 191, in run_from_argv
self.exectured(*args, **options._dict_)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
220, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
351, in handle
   return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
line 52, in handle_noargs
cursor = connection.cursor()
File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
line 15, in complain
raise ImproperlyConfigured("You hav
en't set the database ENGINE setting yet.")
On Sun, Jan 23, 2011 at 8:48 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote:
>>
>> username@debian:~/wikicamps$ python manage.py runserver
>> Validating models
>> 0 errors found
>>
>> Django version 1.2.4, using settings 'wikicamp.settings'
>> Development server is running at http://127.0.0.1:8000/
>> Quit the server with CONTROL-C.
>>
>> It runs fine, but yet I faced problem with the database ENGINE.
>>
>
> Where are you seeing that error because it isn't in what you quote above?
>
> If it is in the browser, paste the Python exception details and traceback
> from the browser. Not everything, just the exception message and traceback
> will do.
>
> In other words, we need to see the actual context in which the real error
> message is displayed and the exact wording of the error message and the
> location.
>
> Graham
>
>
>> On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton 
>> wrote:
>>
>>> Provide  the full error including any Python traceback so we can see
>>> where the error is occurring. If running manage.py runserver, easiest thing
>>> to do is to provide the whole output from running the command.
>>>
>>> Graham
>>>
>>> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>>>
 Still doesn't work. But thank you for trying to help me. It keep giving
 me the same ENGINE configuration that it is not set.

 On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>>
>> Sorry about that... here is what I have in the settings.py ( similiar
>> to what you showed, but mine is abit different in the NAME section):
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME':  'home/username/directory/database'  #
>> Or path to database file if using sqlite3.
>>
>
> You deleted the comma after the string and missing leading slash on
> path. Try:
>
> 'NAME':  '/home/username/directory/database',
>  # Or path to database file if using sqlite3.
>
> Not sure how you didn't just get a syntax error.
>
> Graham
>
>
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for
>> default. Not used with sqlite3.
>> }
>> }
>>
>> Inside the settings.py file, in the template_dirs section, there's a
>> line says os.path.join(os.path.dirname(_file_), 'templates')
>>
>> If I comment that, then there's a error saying it doesn't recognize
>> _file_. I commented that line, then it says that the setting ENGINE has 
>> not
>> been set.
>>
>>
>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>> wrote:
>>
>>>  Rather than have us guess what is in your settings file, post that
>>> whole section. For example:
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),
>>> 

Re: Django Improper Configuration

[Kimberly Harvey]

That doesn't work for me ( very very strange), that why I am very confused
on what is going on with the database itself.

On Sun, Jan 23, 2011 at 8:55 PM, Steven Elliott Jr  wrote:

> I remember that the one time I tried sqlite it complained until I put a .db
> suffix on the name of my database. If you do not specify the full path and
> just specify a name, then it will just create the database file in your
> project's root directory.
>
> So, under name just put:
>
> 'NAME' : 'database.db',
>
> And see if that works.
>
> -Steve
> Sent from my iPhone
>
>
> On Jan 23, 2011, at 9:48 PM, Graham Dumpleton 
> wrote:
>
>
>
> On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote:
>>
>> username@debian:~/wikicamps$ python manage.py runserver
>> Validating models
>> 0 errors found
>>
>> Django version 1.2.4, using settings 'wikicamp.settings'
>> Development server is running at 
>> http://127.0.0.1:8000/
>> Quit the server with CONTROL-C.
>>
>> It runs fine, but yet I faced problem with the database ENGINE.
>>
>
> Where are you seeing that error because it isn't in what you quote above?
>
> If it is in the browser, paste the Python exception details and traceback
> from the browser. Not everything, just the exception message and traceback
> will do.
>
> In other words, we need to see the actual context in which the real error
> message is displayed and the exact wording of the error message and the
> location.
>
> Graham
>
>
>> On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton 
>> wrote:
>>
>>> Provide  the full error including any Python traceback so we can see
>>> where the error is occurring. If running manage.py runserver, easiest thing
>>> to do is to provide the whole output from running the command.
>>>
>>> Graham
>>>
>>> On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>>>
 Still doesn't work. But thank you for trying to help me. It keep giving
 me the same ENGINE configuration that it is not set.

 On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>>
>> Sorry about that... here is what I have in the settings.py ( similiar
>> to what you showed, but mine is abit different in the NAME section):
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME':  'home/username/directory/database'  #
>> Or path to database file if using sqlite3.
>>
>
> You deleted the comma after the string and missing leading slash on
> path. Try:
>
> 'NAME':  '/home/username/directory/database',
>  # Or path to database file if using sqlite3.
>
> Not sure how you didn't just get a syntax error.
>
> Graham
>
>
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for
>> default. Not used with sqlite3.
>> }
>> }
>>
>> Inside the settings.py file, in the template_dirs section, there's a
>> line says os.path.join(os.path.dirname(_file_), 'templates')
>>
>> If I comment that, then there's a error saying it doesn't recognize
>> _file_. I commented that line, then it says that the setting ENGINE has 
>> not
>> been set.
>>
>>
>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>> wrote:
>>
>>>  Rather than have us guess what is in your settings file, post that
>>> whole section. For example:
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3', # Add
>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>> 'NAME': os.path.join(ENVIRON_ROOT, 'db', 'database.db'),
>>>  # Or path to database file if using sqlite3.
>>> 'USER': '',  # Not used with sqlite3.
>>> 'PASSWORD': '',  # Not used with sqlite3.
>>> 'HOST': '',  # Set to empty string for
>>> localhost. Not used with sqlite3.
>>> 'PORT': '',  # Set to empty string for
>>> default. Not used with sqlite3.
>>> }
>>> }
>>>
>>> This will allow everyone to see if you have mucked up some other part
>>> of the settings.
>>>
>>> Graham
>>>
>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>
  I've used the tutorials and it doesn't work. I've done exactly
 what the tutorial says, and it keeps saying that the ENGINE has not 
>

Re: Django Improper Configuration

[Steven Elliott]

Copy and Paste the following to replace your entire DATABASES tuple:

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', 
'NAME': 'database.db', 
'USER': '', 
'PASSWORD': '', 
'HOST': '', 
'PORT': '', 
}
}

it looks like in your configuration you are also missing a comma after the name 
of the database. Remember you must include that comma because this is a tuple.



-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Steven Elliott]

Also, what editor are you using? if its not an IDE-type thing remember to save 
your work in the editor. If you are coming from the Windows programming world 
generally your programs will save when you build and run something in the IDE. 
If you're using just an editor like Emacs, Vim, Gedit, Kate, or whatever it is 
you must remember to save your work after you've made and edit. 


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

It is not working at all, still facing the same configuration problem
(ENGINE IS NOT SET).

On Sun, Jan 23, 2011 at 9:19 PM, Steven Elliott  wrote:

> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
>'default': {
>'ENGINE': 'django.db.backends.sqlite3',
> 'NAME': 'database.db',
>'USER': '',
>'PASSWORD': '',
>'HOST': '',
>'PORT': '',
>}
> }
>
> it looks like in your configuration you are also missing a comma after the
> name of the database. Remember you must include that comma because this is a
> tuple.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>
> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', 
> 'NAME': 'database.db', 
> 'USER': '',   
> 'PASSWORD': '',   
> 'HOST': '',   
> 'PORT': '',   
> }
> }
>
> it looks like in your configuration you are also missing a comma after the 
> name of the database. Remember you must include that comma because this is a 
> tuple.
>

That was already pointed out to them.

The lack of a comma should have resulted in a syntax error, which makes me 
believe, unless they modified the content before posting, that they may be 
modifying a different file to what is being read.

I would like to see them, instead of changing DATABASES yet again, is to add 
at the very end of their settings.py file, the lines:

  print __file__
  print 'DATABASES', DATABASES

This will prove two things. First that the file is being read as the output 
from this should show on stdout when running runserver or syncdb. Second, 
will show what Python is seeing DATABASES as being set to.

if it doesn't show, then wrong file. If shows, but is different to what they 
believe they are setting it to, they could have multiple DATABASES entries 
in file.

Graham

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

I am using pico editior and I've been saving the work by using the control
X.

On Sun, Jan 23, 2011 at 9:25 PM, Steven Elliott  wrote:

> Also, what editor are you using? if its not an IDE-type thing remember to
> save your work in the editor. If you are coming from the Windows programming
> world generally your programs will save when you build and run something in
> the IDE. If you're using just an editor like Emacs, Vim, Gedit, Kate, or
> whatever it is you must remember to save your work after you've made and
> edit.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Steven Elliott]

> That was already pointed out to them.

You're right, sorry my bad -- I just got to my computer and read the thread 
rather than just using my phone.

> The lack of a comma should have resulted in a syntax error, which makes me 
> believe, unless they modified the content before posting, that they may be 
> modifying a different file to what is being read.
> 
> I would like to see them, instead of changing DATABASES yet again, is to add 
> at the very end of their settings.py file, the lines:
> 
>   print __file__
>   print 'DATABASES', DATABASES
> 
> This will prove two things. First that the file is being read as the output 
> from this should show on stdout when running runserver or syncdb. Second, 
> will show what Python is seeing DATABASES as being set to.
> 
> if it doesn't show, then wrong file. If shows, but is different to what they 
> believe they are setting it to, they could have multiple DATABASES entries in 
> file.

Yes, this is excellent advice -- post the output you get from the terminal 
after you've run it. 


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

it says that the _file_ is not defined.

On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>>
>> Copy and Paste the following to replace your entire DATABASES tuple:
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3',
>> 'NAME': 'database.db',
>> 'USER': '',
>> 'PASSWORD': '',
>> 'HOST': '',
>> 'PORT': '',
>> }
>> }
>>
>> it looks like in your configuration you are also missing a comma after the
>> name of the database. Remember you must include that comma because this is a
>> tuple.
>>
>
> That was already pointed out to them.
>
> The lack of a comma should have resulted in a syntax error, which makes me
> believe, unless they modified the content before posting, that they may be
> modifying a different file to what is being read.
>
> I would like to see them, instead of changing DATABASES yet again, is to
> add at the very end of their settings.py file, the lines:
>
>   print __file__
>   print 'DATABASES', DATABASES
>
> This will prove two things. First that the file is being read as the output
> from this should show on stdout when running runserver or syncdb. Second,
> will show what Python is seeing DATABASES as being set to.
>
> if it doesn't show, then wrong file. If shows, but is different to what
> they believe they are setting it to, they could have multiple DATABASES
> entries in file.
>
> Graham
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

That is two underscores, followed by 'file' followed by two underscores. Not 
just a single underscore.

Please try and cut and paste out we give to use and vice versa. In other 
words, provide complete output showing full errors and tracebacks. Such 
information may be meaningful to use even if you think it isn't.

Graham

On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>
> it says that the _file_ is not defined. 
>
> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>>>
>>> Copy and Paste the following to replace your entire DATABASES tuple:
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3', 
>>> 'NAME': 'database.db', 
>>> 'USER': '',   
>>> 'PASSWORD': '',   
>>> 'HOST': '',   
>>> 'PORT': '',   
>>> }
>>> }
>>>
>>> it looks like in your configuration you are also missing a comma after 
>>> the name of the database. Remember you must include that comma because this 
>>> is a tuple.
>>>
>>
>> That was already pointed out to them.
>>
>> The lack of a comma should have resulted in a syntax error, which makes me 
>> believe, unless they modified the content before posting, that they may be 
>> modifying a different file to what is being read.
>>
>> I would like to see them, instead of changing DATABASES yet again, is to 
>> add at the very end of their settings.py file, the lines:
>>
>>   print __file__
>>   print 'DATABASES', DATABASES
>>
>> This will prove two things. First that the file is being read as the 
>> output from this should show on stdout when running runserver or syncdb. 
>> Second, will show what Python is seeing DATABASES as being set to.
>>
>> if it doesn't show, then wrong file. If shows, but is different to what 
>> they believe they are setting it to, they could have multiple DATABASES 
>> entries in file.
>>
>> Graham
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To post to this group, send email to django...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

I've provided the full errors in the post, it is there. ( same errors as
I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as
I'm encountering the same after I've copied and paste the print inside the
settings.py file at the end)

On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

> That is two underscores, followed by 'file' followed by two underscores.
> Not just a single underscore.
>
> Please try and cut and paste out we give to use and vice versa. In other
> words, provide complete output showing full errors and tracebacks. Such
> information may be meaningful to use even if you think it isn't.
>
> Graham
>
>
> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>
>> it says that the _file_ is not defined.
>>
>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
>> wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:

 Copy and Paste the following to replace your entire DATABASES tuple:

 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'database.db',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'PORT': '',
 }
 }

 it looks like in your configuration you are also missing a comma after
 the name of the database. Remember you must include that comma because this
 is a tuple.

>>>
>>> That was already pointed out to them.
>>>
>>> The lack of a comma should have resulted in a syntax error, which makes
>>> me believe, unless they modified the content before posting, that they may
>>> be modifying a different file to what is being read.
>>>
>>> I would like to see them, instead of changing DATABASES yet again, is to
>>> add at the very end of their settings.py file, the lines:
>>>
>>>   print __file__
>>>   print 'DATABASES', DATABASES
>>>
>>> This will prove two things. First that the file is being read as the
>>> output from this should show on stdout when running runserver or syncdb.
>>> Second, will show what Python is seeing DATABASES as being set to.
>>>
>>> if it doesn't show, then wrong file. If shows, but is different to what
>>> they believe they are setting it to, they could have multiple DATABASES
>>> entries in file.
>>>
>>> Graham
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

Are you saying that those two print statements you were told to add are not 
causing anything additional to be displayed on the screen when you run both 
runserver and syncdb?

This is why I asked you to provide the output again. You may not understand 
what we are looking for. Don't care about what the error is at the point but 
the information that those print statements should have output.

Graham

On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>
> I've provided the full errors in the post, it is there. ( same errors as 
> I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as 
> I'm encountering the same after I've copied and paste the print inside the 
> settings.py file at the end)
>
> On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton 
> wrote:
>
>> That is two underscores, followed by 'file' followed by two underscores. 
>> Not just a single underscore.
>>
>> Please try and cut and paste out we give to use and vice versa. In other 
>> words, provide complete output showing full errors and tracebacks. Such 
>> information may be meaningful to use even if you think it isn't.
>>
>> Graham
>>
>>
>> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>
>>> it says that the _file_ is not defined. 
>>>
>>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton wrote:
>>>


 On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>
> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', 
> 'NAME': 'database.db', 
> 'USER': '',   
> 'PASSWORD': '',   
> 'HOST': '',   
> 'PORT': '',   
> }
> }
>
> it looks like in your configuration you are also missing a comma after 
> the name of the database. Remember you must include that comma because 
> this 
> is a tuple.
>

 That was already pointed out to them.

 The lack of a comma should have resulted in a syntax error, which makes 
 me believe, unless they modified the content before posting, that they may 
 be modifying a different file to what is being read.

 I would like to see them, instead of changing DATABASES yet again, is to 
 add at the very end of their settings.py file, the lines:

   print __file__
   print 'DATABASES', DATABASES

 This will prove two things. First that the file is being read as the 
 output from this should show on stdout when running runserver or syncdb. 
 Second, will show what Python is seeing DATABASES as being set to.

 if it doesn't show, then wrong file. If shows, but is different to what 
 they believe they are setting it to, they could have multiple DATABASES 
 entries in file.

 Graham

  -- 
 You received this message because you are subscribed to the Google 
 Groups "Django users" group.
 To post to this group, send email to djan...@googlegroups.com.
 To unsubscribe from this group, send email to 
 django-...@googlegroups.com.

 For more options, visit this group at 
 http://groups.google.com/group/django-users?hl=en.

>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To post to this group, send email to django...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Steven Elliott Jr]

Just curious if you've done a python tutorial yet? It's hard to really 
understand Django well unless you have at least some working knowledge of 
python. You will most definitely struggle later on when things become more 
complicated with your app. The framework is great for repetitive tasks but 
you're going to need to know how to write python code if you're to get 
anywhere. 

It's definitely possible to learn both at the same time but I'd read through, 
and work through a few python tutorials first then come back to Django. 

I know this is probably not what you'd like to hear and it's just my two cents 
so... 

Anyway, keep posting and we will try to help. 

-Steven

On Jan 23, 2011, at 10:40 PM, Graham Dumpleton  
wrote:

> That is two underscores, followed by 'file' followed by two underscores. Not 
> just a single underscore.
> 
> Please try and cut and paste out we give to use and vice versa. In other 
> words, provide complete output showing full errors and tracebacks. Such 
> information may be meaningful to use even if you think it isn't.
> 
> Graham
> 
> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
> it says that the _file_ is not defined. 
> 
> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton  
> wrote:
> 
> 
> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
> Copy and Paste the following to replace your entire DATABASES tuple:
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', 
> 'NAME': 'database.db', 
> 'USER': '',   
> 'PASSWORD': '',   
> 'HOST': '',   
> 'PORT': '',   
> }
> }
> 
> it looks like in your configuration you are also missing a comma after the 
> name of the database. Remember you must include that comma because this is a 
> tuple.
> 
> 
> That was already pointed out to them.
> 
> The lack of a comma should have resulted in a syntax error, which makes me 
> believe, unless they modified the content before posting, that they may be 
> modifying a different file to what is being read.
> 
> I would like to see them, instead of changing DATABASES yet again, is to add 
> at the very end of their settings.py file, the lines:
> 
>   print __file__
>   print 'DATABASES', DATABASES
> 
> This will prove two things. First that the file is being read as the output 
> from this should show on stdout when running runserver or syncdb. Second, 
> will show what Python is seeing DATABASES as being set to.
> 
> if it doesn't show, then wrong file. If shows, but is different to what they 
> believe they are setting it to, they could have multiple DATABASES entries in 
> file.
> 
> Graham
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>
> Are you saying that those two print statements you were told to add are not 
> causing anything additional to be displayed on the screen when you run both 
> runserver and syncdb?
>
> This is why I asked you to provide the output again. You may not understand 
> what we are looking for. Don't care about what the error is at the point but 
> the information that those print statements should have output.
>

For the record, I would expect to see those print statements produce output 
at least twice. This is because settings.py actually gets imported multiple 
times. So, for example I see:

Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
Traceback (most recent call last):
  File "manage.py", line 2, in 
from django.core.management import execute_manager
ImportError: No module named django.core.management
Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
/Library/WebServer/Sites/django-2/projects/mysite/settings.py
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
/Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
/Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
/Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
Validating models...

0 errors found
Django version 1.3 beta 1, using settings 'mysite.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.


^C(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py syncdb
/Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
/Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
'PASSWORD': '', 'PORT': ''}}
Creating tables ...
Installing custom SQL ...
Installing indexes ...
No fixtures found.

Don't get me started on the multiple imports of settings.py file. :-(

Graham
 

On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>>
>> I've provided the full errors in the post, it is there. ( same errors as 
>> I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as 
>> I'm encountering the same after I've copied and paste the print inside the 
>> settings.py file at the end)
>>
>> On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton wrote:
>>
>>> That is two underscores, followed by 'file' followed by two underscores. 
>>> Not just a single underscore.
>>>
>>> Please try and cut and paste out we give to use and vice versa. In other 
>>> words, provide complete output showing full errors and tracebacks. Such 
>>> information may be meaningful to use even if you think it isn't.
>>>
>>> Graham
>>>
>>>
>>> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>>
 it says that the _file_ is not defined. 

 On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton wrote:

>
>
> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>>
>> Copy and Paste the following to replace your entire DATABASES tuple:
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3', 
>> 'NAME': 'database.db', 
>> 'USER': '',   
>> 'PASSWORD': '',   
>> 'HOST': '',   
>> 'PORT': '',   
>> }
>> }
>>
>> it looks like in your configuration you are also missing a comma after 
>> the name of the database. Remember you must include that comma because 
>> this 
>> is a tuple.
>>
>
> That was already pointed out to them.
>
> The lack of a comma should have resulted in a syntax error, which makes 
> me believe, unless they modified the content before posting, that they 
> may 
> be modifying a different file to what is being read.
>
> I would like to see them, instead of chan

Re: Django Improper Configuration

[Kimberly Harvey]

Thank you for the advices. I've done some Python codes in the past and
recently. I already have a Python code that I will need to use to create a
Django website ( response to Steven).

(Response to Graham):
Traceback ( most recent call last):
 File "manage.py", line 11, in 
execute_manager(settings)
File "/usr/lib/python2.5/site-
packages/django/core/management/_init_.py", line 438, in execute manager
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
379, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 191, in run_from_argv
self.exectured(*args, **options._dict_)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
220, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
351, in handle
   return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
line 52, in handle_noargs
cursor = connection.cursor()
File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
line 15, in complain
raise ImproperlyConfigured("You hav
en't set the database ENGINE setting yet.")


On Sun, Jan 23, 2011 at 9:54 PM, Steven Elliott Jr  wrote:

> Just curious if you've done a python tutorial yet? It's hard to really
> understand Django well unless you have at least some working knowledge of
> python. You will most definitely struggle later on when things become more
> complicated with your app. The framework is great for repetitive tasks but
> you're going to need to know how to write python code if you're to get
> anywhere.
>
> It's definitely possible to learn both at the same time but I'd read
> through, and work through a few python tutorials first then come back to
> Django.
>
> I know this is probably not what you'd like to hear and it's just my two
> cents so...
>
> Anyway, keep posting and we will try to help.
>
> -Steven
>
> On Jan 23, 2011, at 10:40 PM, Graham Dumpleton 
> wrote:
>
> That is two underscores, followed by 'file' followed by two underscores.
> Not just a single underscore.
>
> Please try and cut and paste out we give to use and vice versa. In other
> words, provide complete output showing full errors and tracebacks. Such
> information may be meaningful to use even if you think it isn't.
>
> Graham
>
> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>
>> it says that the _file_ is not defined.
>>
>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
>> wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:

 Copy and Paste the following to replace your entire DATABASES tuple:

 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'database.db',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'PORT': '',
 }
 }

 it looks like in your configuration you are also missing a comma after
 the name of the database. Remember you must include that comma because this
 is a tuple.

>>>
>>> That was already pointed out to them.
>>>
>>> The lack of a comma should have resulted in a syntax error, which makes
>>> me believe, unless they modified the content before posting, that they may
>>> be modifying a different file to what is being read.
>>>
>>> I would like to see them, instead of changing DATABASES yet again, is to
>>> add at the very end of their settings.py file, the lines:
>>>
>>>   print __file__
>>>   print 'DATABASES', DATABASES
>>>
>>> This will prove two things. First that the file is being read as the
>>> output from this should show on stdout when running runserver or syncdb.
>>> Second, will show what Python is seeing DATABASES as being set to.
>>>
>>> if it doesn't show, then wrong file. If shows, but is different to what
>>> they believe they are setting it to, they could have multiple DATABASES
>>> entries in file.
>>>
>>> Graham
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>> For more options, visit this group at
>>> 
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>  --
> You received this message because you are subs

Re: Django Improper Configuration

[Kimberly Harvey]

Traceback ( most recent call last):
 File "manage.py", line 11, in 
execute_manager(settings)
File "/usr/lib/python2.5/site-
packages/django/core/management/_init_.py", line 438, in execute manager
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
379, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 191, in run_from_argv
self.exectured(*args, **options._dict_)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
220, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
351, in handle
   return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
line 52, in handle_noargs
cursor = connection.cursor()
File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
line 15, in complain
raise ImproperlyConfigured("You hav
en't set the database ENGINE setting yet.")

THE ABOVE IS when I typed python manage.py syncdb




Below is when I ran the python manage.py runserver
/home/username/wikicamp/settings.pyc
DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
validating models...
0 errors found

Django version 1.2.4, using settings 'wikicamp.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL -C

Those are the outputs after y


On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>>
>> Are you saying that those two print statements you were told to add are
>> not causing anything additional to be displayed on the screen when you run
>> both runserver and syncdb?
>>
>> This is why I asked you to provide the output again. You may not
>> understand what we are looking for. Don't care about what the error is at
>> the point but the information that those print statements should have
>> output.
>>
>
> For the record, I would expect to see those print statements produce output
> at least twice. This is because settings.py actually gets imported multiple
> times. So, for example I see:
>
> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
> Traceback (most recent call last):
>   File "manage.py", line 2, in 
> from django.core.management import execute_manager
> ImportError: No module named django.core.management
> Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
> (django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
> /Library/WebServer/Sites/django-2/projects/mysite/settings.py
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> Validating models...
>
> 0 errors found
> Django version 1.3 beta 1, using settings 'mysite.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
>
>
> ^C(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py syncdb
> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> No fixtures found.
>
> Don't get me started on the multiple imports of settings.py file. :-(
>
> Graham
>
>
> On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>>
>>> I've provided the full errors in the post, it is there. ( same errors as
>>> I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as
>>> I'm encountering the same after I'v

Re: Django Improper Configuration

[Kimberly Harvey]

The output was produced with the print __file__ and print 'DATABASES',
DATABASES at the end of the settings.py file.

On Sun, Jan 23, 2011 at 10:18 PM, Kimberly Harvey wrote:

> Traceback ( most recent call last):
>  File "manage.py", line 11, in 
> execute_manager(settings)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/_init_.py", line 438, in execute manager
> File
> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
> 379, in execute
>   self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 191, in run_from_argv
> self.exectured(*args, **options._dict_)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 220, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 351, in handle
>return self.handle_noargs(**options)
> File
> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
> line 52, in handle_noargs
> cursor = connection.cursor()
> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
> line 15, in complain
> raise ImproperlyConfigured("You hav
> en't set the database ENGINE setting yet.")
>
> THE ABOVE IS when I typed python manage.py syncdb
>
>
>
>
> Below is when I ran the python manage.py runserver
> /home/username/wikicamp/settings.pyc
> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>
> validating models...
> 0 errors found
>
> Django version 1.2.4, using settings 'wikicamp.settings'
>
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL -C
>
> Those are the outputs after y
>
>
> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>>>
>>> Are you saying that those two print statements you were told to add are
>>> not causing anything additional to be displayed on the screen when you run
>>> both runserver and syncdb?
>>>
>>> This is why I asked you to provide the output again. You may not
>>> understand what we are looking for. Don't care about what the error is at
>>> the point but the information that those print statements should have
>>> output.
>>>
>>
>> For the record, I would expect to see those print statements produce
>> output at least twice. This is because settings.py actually gets imported
>> multiple times. So, for example I see:
>>
>> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> Traceback (most recent call last):
>>   File "manage.py", line 2, in 
>> from django.core.management import execute_manager
>> ImportError: No module named django.core.management
>> Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
>> (django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.py
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> Validating models...
>>
>> 0 errors found
>> Django version 1.3 beta 1, using settings 'mysite.settings'
>> Development server is running at http://127.0.0.1:8000/
>> Quit the server with CONTROL-C.
>>
>>
>> ^C(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py syncdb
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> Creating tables ...
>> Installing custom SQL ...
>> Installing indexes ...
>> No fixtures found.
>>
>> Don't get me start

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>
> Traceback ( most recent call last):
>  File "manage.py", line 11, in 
> execute_manager(settings)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/_init_.py", line 438, in execute manager
> File 
> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line 
> 379, in execute
>   self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
> line 191, in run_from_argv
> self.exectured(*args, **options._dict_)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
> line 220, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
> line 351, in handle
>return self.handle_noargs(**options)
> File 
> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py", 
> line 52, in handle_noargs
> cursor = connection.cursor()
> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", 
> line 15, in complain
> raise ImproperlyConfigured("You hav
> en't set the database ENGINE setting yet.")
>
> THE ABOVE IS when I typed python manage.py syncdb
>

Okay, if you definitely 100% aren't seeing something like:

/home/username/wikicamp/settings.pyc
DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}

when running syncdb, then having a hard time explaining why it isn't being 
loaded.

Please do the following and provide the output:

  pwd

This is to show us the directory you are in when you are running runserver 
and syncdb.

  echo $PYTHONPATH

This is to show us if you have a custom Python module search path set in 
your environment.

  echo $DJANGO_SETTINGS_MODULE

This is show is if you are setting where Django should find its settings 
module.

Now run 'python' from the command line and do the following, providing the 
output to us:

  import settings
  print settings.__file__

  import wikicamp.settings
  print wikicamp.settings.__file__

These might produce exceptions depending on where you current working 
directory is.

This is to show whether you may have created a backup copy of settings.py 
file somewhere which is being found instead of that in same directory as 
manage.py.

Finally, if you have modified manage.py, tell is what you have changed it 
to.

Graham

Below is when I ran the python manage.py runserver
> /home/username/wikicamp/settings.pyc
> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
> validating models...
> 0 errors found
>
> Django version 1.2.4, using settings 'wikicamp.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL -C
>
> Those are the outputs after y
>
>
> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>>>
>>> Are you saying that those two print statements you were told to add are 
>>> not causing anything additional to be displayed on the screen when you run 
>>> both runserver and syncdb?
>>>
>>> This is why I asked you to provide the output again. You may not 
>>> understand what we are looking for. Don't care about what the error is at 
>>> the point but the information that those print statements should have 
>>> output.
>>>
>>
>> For the record, I would expect to see those print statements produce 
>> output at least twice. This is because settings.py actually gets imported 
>> multiple times. So, for example I see:
>>
>> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> Traceback (most recent call last):
>>   File "manage.py", line 2, in 
>> from django.core.management import execute_manager
>> ImportError: No module named django.core.management
>> Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
>> (django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.py
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '', 
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DA

Re: Django Improper Configuration

[Kimberly Harvey]

Please do the following and provide the output:

  pwd

MY OUTPUT: /home/username/wikicamp

Now run 'python' from the command line and do the following, providing the
output to us:

  import settings
  print settings.__file__

  import wikicamp.settings
  print wikicamp.settings.__file__

after importing setting
print settings.__file__
OUTPUT: settings.pyc

 import wikicamp.settings
  print wikicamp.settings.__file__

OUTPUT: wikicamp/settings.pyc

These might produce exceptions depending on where you current working
directory is.

This is to show whether you may have created a backup copy of settings.py
file somewhere which is being found instead of that in same directory as
manage.py.

Finally, if you have modified manage.py, tell is what you have changed it
to.



On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>>
>> Traceback ( most recent call last):
>>  File "manage.py", line 11, in 
>> execute_manager(settings)
>> File "/usr/lib/python2.5/site-
>> packages/django/core/management/_init_.py", line 438, in execute manager
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
>> 379, in execute
>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 191,
>> in run_from_argv
>> self.exectured(*args, **options._dict_)
>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>> line 220, in execute
>> output = self.handle(*args, **options)
>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>> line 351, in handle
>>return self.handle_noargs(**options)
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>> line 52, in handle_noargs
>> cursor = connection.cursor()
>> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
>> line 15, in complain
>> raise ImproperlyConfigured("You hav
>> en't set the database ENGINE setting yet.")
>>
>> THE ABOVE IS when I typed python manage.py syncdb
>>
>
> Okay, if you definitely 100% aren't seeing something like:
>
> /home/username/wikicamp/settings.pyc
> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>
> when running syncdb, then having a hard time explaining why it isn't being
> loaded.
>
> Please do the following and provide the output:
>
>   pwd
>
> This is to show us the directory you are in when you are running runserver
> and syncdb.
>
>   echo $PYTHONPATH
>
> This is to show us if you have a custom Python module search path set in
> your environment.
>
>   echo $DJANGO_SETTINGS_MODULE
>
> This is show is if you are setting where Django should find its settings
> module.
>
> Now run 'python' from the command line and do the following, providing the
> output to us:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> These might produce exceptions depending on where you current working
> directory is.
>
> This is to show whether you may have created a backup copy of settings.py
> file somewhere which is being found instead of that in same directory as
> manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed it
> to.
>
> Graham
>
> Below is when I ran the python manage.py runserver
>> /home/username/wikicamp/settings.pyc
>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>> validating models...
>> 0 errors found
>>
>> Django version 1.2.4, using settings 'wikicamp.settings'
>> Development server is running at http://127.0.0.1:8000/
>> Quit the server with CONTROL -C
>>
>> Those are the outputs after y
>>
>>
>> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:

 Are you saying that those two print statements you were told to add are
 not causing anything additional to be displayed on the screen when you run
 both runserver and syncdb?

 This is why I asked you to provide the output again. You may not
 understand what we are looking for. Don't care about what the error is at
 the point but the information that those print statements should have
 output.

>>>
>>> For the record, I would expect to see those print statements produce
>>> output at least twice. This is because settings.py actually gets imported
>>> multiple times. So, for example I see:
>>>
>>> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>>> Traceback (most recent call last):
>>>   File "manage.py", line 2, in 
>>> from django.core.management import execute_manager
>>> ImportError: No module named django.core.ma

Re: Django Improper Configuration

[Kimberly Harvey]

I did not modified the manage.py file





On Sun, Jan 23, 2011 at 10:44 PM, Kimberly Harvey wrote:

> Please do the following and provide the output:
>
>   pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following, providing the
> output to us:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> after importing setting
> print settings.__file__
> OUTPUT: settings.pyc
>
>  import wikicamp.settings
>   print wikicamp.settings.__file__
>
> OUTPUT: wikicamp/settings.pyc
>
> These might produce exceptions depending on where you current working
> directory is.
>
> This is to show whether you may have created a backup copy of settings.py
> file somewhere which is being found instead of that in same directory as
> manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed it
> to.
>
>
>
> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>>>
>>> Traceback ( most recent call last):
>>>  File "manage.py", line 11, in 
>>> execute_manager(settings)
>>> File "/usr/lib/python2.5/site-
>>> packages/django/core/management/_init_.py", line 438, in execute manager
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
>>> 379, in execute
>>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 191,
>>> in run_from_argv
>>> self.exectured(*args, **options._dict_)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>> line 220, in execute
>>> output = self.handle(*args, **options)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>> line 351, in handle
>>>return self.handle_noargs(**options)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>>> line 52, in handle_noargs
>>> cursor = connection.cursor()
>>> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
>>> line 15, in complain
>>> raise ImproperlyConfigured("You hav
>>> en't set the database ENGINE setting yet.")
>>>
>>> THE ABOVE IS when I typed python manage.py syncdb
>>>
>>
>> Okay, if you definitely 100% aren't seeing something like:
>>
>> /home/username/wikicamp/settings.pyc
>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>
>> when running syncdb, then having a hard time explaining why it isn't being
>> loaded.
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> This is to show us the directory you are in when you are running runserver
>> and syncdb.
>>
>>   echo $PYTHONPATH
>>
>> This is to show us if you have a custom Python module search path set in
>> your environment.
>>
>>   echo $DJANGO_SETTINGS_MODULE
>>
>> This is show is if you are setting where Django should find its settings
>> module.
>>
>> Now run 'python' from the command line and do the following, providing the
>> output to us:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> These might produce exceptions depending on where you current working
>> directory is.
>>
>> This is to show whether you may have created a backup copy of settings.py
>> file somewhere which is being found instead of that in same directory as
>> manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed it
>> to.
>>
>> Graham
>>
>> Below is when I ran the python manage.py runserver
>>> /home/username/wikicamp/settings.pyc
>>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>> validating models...
>>> 0 errors found
>>>
>>> Django version 1.2.4, using settings 'wikicamp.settings'
>>> Development server is running at http://127.0.0.1:8000/
>>> Quit the server with CONTROL -C
>>>
>>> Those are the outputs after y
>>>
>>>
>>> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton <
>>> graham.d...@gmail.com> wrote:
>>>


 On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>
> Are you saying that those two print statements you were told to add are
> not causing anything additional to be displayed on the screen when you run
> both runserver and syncdb?
>
> This is why I asked you to provide the output again. You may not
> understand what we are looking for. Don't care about what the error is at
> the point but the information that those print statements should have
> output.
>

 For the record, I would expect to see those print statements produce
 output at least twice. This is because settings.py actually gets 

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>
> Please do the following and provide the output:
>
>   pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following, providing the 
> output to us:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> after importing setting
> print settings.__file__
> OUTPUT: settings.pyc
>
>  import wikicamp.settings 
>   print wikicamp.settings.__file__
>
> OUTPUT: wikicamp/settings.pyc
>

Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE 
was set to in environment to eliminate them as cause, but the above suggests 
that you have two Django projects created. One is at:

  /home/username/wikicamp

and the other at:

  /home/username/wikicamp/wikicamp

Can you confirm this by indicating whether then file:

  /home/username/wikicamp/wikicamp/settings.py

exists.

If this is write, then what is happening is that when syncb is being running 
it is actually picking up the settings file from that second site nested 
within the first.

If that is what has been done, then do:

  mv /home/username/wikicamp/wikicamp /home/username/wikicamp/wikicamp.broken

Also be aware that you shouldn't create Django apps with the same name as 
the project either, as the duplication of name can cause problems there as 
well, although for an app you wouldn't have a settings.py file in it, which 
in this case it seems you do.

Graham
 

> These might produce exceptions depending on where you current working 
> directory is.
>
> This is to show whether you may have created a backup copy of settings.py 
> file somewhere which is being found instead of that in same directory as 
> manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed it 
> to.
>
>
>
> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>>>
>>> Traceback ( most recent call last):
>>>  File "manage.py", line 11, in 
>>> execute_manager(settings)
>>> File "/usr/lib/python2.5/site-
>>> packages/django/core/management/_init_.py", line 438, in execute manager
>>> File 
>>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line 
>>> 379, in execute
>>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>>> File 
>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>>> 191, 
>>> in run_from_argv
>>> self.exectured(*args, **options._dict_)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
>>> line 220, in execute
>>> output = self.handle(*args, **options)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
>>> line 351, in handle
>>>return self.handle_noargs(**options)
>>> File 
>>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>>>  
>>> line 52, in handle_noargs
>>> cursor = connection.cursor()
>>> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", 
>>> line 15, in complain
>>> raise ImproperlyConfigured("You hav
>>> en't set the database ENGINE setting yet.")
>>>
>>> THE ABOVE IS when I typed python manage.py syncdb
>>>
>>
>> Okay, if you definitely 100% aren't seeing something like:
>>
>> /home/username/wikicamp/settings.pyc
>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>
>> when running syncdb, then having a hard time explaining why it isn't being 
>> loaded.
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> This is to show us the directory you are in when you are running runserver 
>> and syncdb.
>>
>>   echo $PYTHONPATH
>>
>> This is to show us if you have a custom Python module search path set in 
>> your environment.
>>
>>   echo $DJANGO_SETTINGS_MODULE
>>
>> This is show is if you are setting where Django should find its settings 
>> module.
>>
>> Now run 'python' from the command line and do the following, providing the 
>> output to us:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> These might produce exceptions depending on where you current working 
>> directory is.
>>
>> This is to show whether you may have created a backup copy of settings.py 
>> file somewhere which is being found instead of that in same directory as 
>> manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed it 
>> to.
>>
>> Graham
>>
>> Below is when I ran the python manage.py runserver
>>> /home/username/wikicamp/settings.pyc
>>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 
>>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>> validating models...
>>> 0 errors found
>>>
>>> Django version 1.2.4, using settings 'wikica

Re: Django Improper Configuration

[Kimberly Harvey]

Sorry about that, there is nothing showing for either  echo $PYTHONPATH and
echo $DJANGO_SETTINGS_MODULE

I am currently reading your messages.

On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> MY OUTPUT: /home/username/wikicamp
>>
>> Now run 'python' from the command line and do the following, providing the
>> output to us:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> after importing setting
>> print settings.__file__
>> OUTPUT: settings.pyc
>>
>>  import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> OUTPUT: wikicamp/settings.pyc
>>
>
> Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE
> was set to in environment to eliminate them as cause, but the above suggests
> that you have two Django projects created. One is at:
>
>   /home/username/wikicamp
>
> and the other at:
>
>   /home/username/wikicamp/wikicamp
>
> Can you confirm this by indicating whether then file:
>
>   /home/username/wikicamp/wikicamp/settings.py
>
> exists.
>
> If this is write, then what is happening is that when syncb is being
> running it is actually picking up the settings file from that second site
> nested within the first.
>
> If that is what has been done, then do:
>
>
>   mv /home/username/wikicamp/wikicamp /home/username/wikicamp/wikicamp.broken
>
> Also be aware that you shouldn't create Django apps with the same name as
> the project either, as the duplication of name can cause problems there as
> well, although for an app you wouldn't have a settings.py file in it, which
> in this case it seems you do.
>
> Graham
>
>
>> These might produce exceptions depending on where you current working
>> directory is.
>>
>> This is to show whether you may have created a backup copy of settings.py
>> file somewhere which is being found instead of that in same directory as
>> manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed it
>> to.
>>
>>
>>
>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:

 Traceback ( most recent call last):
  File "manage.py", line 11, in 
 execute_manager(settings)
 File "/usr/lib/python2.5/site-
 packages/django/core/management/_init_.py", line 438, in execute manager
 File
 "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
 379, in execute
   self.fetch_command(subcommand).run_from_argv(self.argv)
 File
 "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
 191,
 in run_from_argv
 self.exectured(*args, **options._dict_)
 File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
 line 220, in execute
 output = self.handle(*args, **options)
 File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
 line 351, in handle
return self.handle_noargs(**options)
 File
 "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
 line 52, in handle_noargs
 cursor = connection.cursor()
 File
 "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", line
 15, in complain
 raise ImproperlyConfigured("You hav
 en't set the database ENGINE setting yet.")

 THE ABOVE IS when I typed python manage.py syncdb

>>>
>>> Okay, if you definitely 100% aren't seeing something like:
>>>
>>> /home/username/wikicamp/settings.pyc
>>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>>
>>> when running syncdb, then having a hard time explaining why it isn't
>>> being loaded.
>>>
>>> Please do the following and provide the output:
>>>
>>>   pwd
>>>
>>> This is to show us the directory you are in when you are running
>>> runserver and syncdb.
>>>
>>>   echo $PYTHONPATH
>>>
>>> This is to show us if you have a custom Python module search path set in
>>> your environment.
>>>
>>>   echo $DJANGO_SETTINGS_MODULE
>>>
>>> This is show is if you are setting where Django should find its settings
>>> module.
>>>
>>> Now run 'python' from the command line and do the following, providing
>>> the output to us:
>>>
>>>   import settings
>>>   print settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> These might produce exceptions depending on where you current working
>>> directory is.
>>>
>>> This is to show whether you may have created a backup copy of settings.py
>>> file somewhere which is being found instead of that in same directory as
>>> manage.py.
>>>
>>> Finally, if you have modified manage.py, tell is what

Re: Django Improper Configuration

[Kimberly Harvey]

  /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST

WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
settings.py is there.


On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:

> Sorry about that, there is nothing showing for either  echo $PYTHONPATH
> and  echo $DJANGO_SETTINGS_MODULE
>
> I am currently reading your messages.
>
>
> On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>>
>>> Please do the following and provide the output:
>>>
>>>   pwd
>>>
>>> MY OUTPUT: /home/username/wikicamp
>>>
>>> Now run 'python' from the command line and do the following, providing
>>> the output to us:
>>>
>>>   import settings
>>>   print settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> after importing setting
>>> print settings.__file__
>>> OUTPUT: settings.pyc
>>>
>>>  import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> OUTPUT: wikicamp/settings.pyc
>>>
>>
>> Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE
>> was set to in environment to eliminate them as cause, but the above suggests
>> that you have two Django projects created. One is at:
>>
>>   /home/username/wikicamp
>>
>> and the other at:
>>
>>   /home/username/wikicamp/wikicamp
>>
>> Can you confirm this by indicating whether then file:
>>
>>   /home/username/wikicamp/wikicamp/settings.py
>>
>> exists.
>>
>> If this is write, then what is happening is that when syncb is being
>> running it is actually picking up the settings file from that second site
>> nested within the first.
>>
>> If that is what has been done, then do:
>>
>>
>>   mv /home/username/wikicamp/wikicamp /home/username/wikicamp/wikicamp.broken
>>
>> Also be aware that you shouldn't create Django apps with the same name as
>> the project either, as the duplication of name can cause problems there as
>> well, although for an app you wouldn't have a settings.py file in it, which
>> in this case it seems you do.
>>
>> Graham
>>
>>
>>> These might produce exceptions depending on where you current working
>>> directory is.
>>>
>>> This is to show whether you may have created a backup copy of settings.py
>>> file somewhere which is being found instead of that in same directory as
>>> manage.py.
>>>
>>> Finally, if you have modified manage.py, tell is what you have changed it
>>> to.
>>>
>>>
>>>
>>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
>>> graham.d...@gmail.com> wrote:
>>>


 On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>
> Traceback ( most recent call last):
>  File "manage.py", line 11, in 
> execute_manager(settings)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/_init_.py", line 438, in execute
> manager
> File
> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
> 379, in execute
>   self.fetch_command(subcommand).run_from_argv(self.argv)
> File
> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
> 191,
> in run_from_argv
> self.exectured(*args, **options._dict_)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 220, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 351, in handle
>return self.handle_noargs(**options)
> File
> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
> line 52, in handle_noargs
> cursor = connection.cursor()
> File
> "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", line
> 15, in complain
> raise ImproperlyConfigured("You hav
> en't set the database ENGINE setting yet.")
>
> THE ABOVE IS when I typed python manage.py syncdb
>

 Okay, if you definitely 100% aren't seeing something like:

 /home/username/wikicamp/settings.pyc
 DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}

 when running syncdb, then having a hard time explaining why it isn't
 being loaded.

 Please do the following and provide the output:

   pwd

 This is to show us the directory you are in when you are running
 runserver and syncdb.

   echo $PYTHONPATH

 This is to show us if you have a custom Python module search path set in
 your environment.

   echo $DJANGO_SETTINGS_MODULE

 This is show is if you are setting where Django should find its settings
 module.

 Now run 'python' from the command line and do the following, providing
 the output to us:

   import settings
   print settings.

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>
>
>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST
>
> WHAT DOES EXIST: /home/username/wikicamp and inside that directory, 
> settings.py is there.
>

Earlier you said you got:

  import settings
  print settings.__file__

  import wikicamp.settings
  print wikicamp.settings.__file__

  after importing setting
  print settings.__file__
  OUTPUT: settings.pyc

  import wikicamp.settings
  print wikicamp.settings.__file__

  OUTPUT: wikicamp/settings.pyc

What directory did you do that from.

If you didn't run this from inside of site directory as was expecting and 
you did it from your home directory, then you have a settings.py sitting in 
your home directory which is the problem. Rename any settings.py file you 
home directory to something else.

  mv ~/settings.py ~/settings.py.broken

In short, you have more than one settings.py file somewhere where it is 
being found and the second one is causing a conflict.

Graham
 

> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
>
>> Sorry about that, there is nothing showing for either  echo $PYTHONPATH 
>> and  echo $DJANGO_SETTINGS_MODULE
>>
>> I am currently reading your messages.
>>
>>
>> On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:

 Please do the following and provide the output:

   pwd

 MY OUTPUT: /home/username/wikicamp

 Now run 'python' from the command line and do the following, providing 
 the output to us:

   import settings
   print settings.__file__

   import wikicamp.settings
   print wikicamp.settings.__file__

 after importing setting
 print settings.__file__
 OUTPUT: settings.pyc

  import wikicamp.settings 
   print wikicamp.settings.__file__

 OUTPUT: wikicamp/settings.pyc

>>>
>>> Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE 
>>> was set to in environment to eliminate them as cause, but the above 
>>> suggests 
>>> that you have two Django projects created. One is at:
>>>
>>>   /home/username/wikicamp
>>>
>>> and the other at:
>>>
>>>   /home/username/wikicamp/wikicamp
>>>
>>> Can you confirm this by indicating whether then file:
>>>
>>>   /home/username/wikicamp/wikicamp/settings.py
>>>
>>> exists.
>>>
>>> If this is write, then what is happening is that when syncb is being 
>>> running it is actually picking up the settings file from that second site 
>>> nested within the first.
>>>
>>> If that is what has been done, then do:
>>>
>>>
>>>   mv /home/username/wikicamp/wikicamp 
>>> /home/username/wikicamp/wikicamp.broken
>>>
>>> Also be aware that you shouldn't create Django apps with the same name as 
>>> the project either, as the duplication of name can cause problems there as 
>>> well, although for an app you wouldn't have a settings.py file in it, which 
>>> in this case it seems you do.
>>>
>>> Graham
>>>  
>>>
 These might produce exceptions depending on where you current working 
 directory is.

 This is to show whether you may have created a backup copy of 
 settings.py file somewhere which is being found instead of that in same 
 directory as manage.py.

 Finally, if you have modified manage.py, tell is what you have changed 
 it to.



 On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>>
>> Traceback ( most recent call last):
>>  File "manage.py", line 11, in 
>> execute_manager(settings)
>> File "/usr/lib/python2.5/site-
>> packages/django/core/management/_init_.py", line 438, in execute 
>> manager
>> File 
>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", 
>> line 
>> 379, in execute
>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>> File 
>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>> 191, 
>> in run_from_argv
>> self.exectured(*args, **options._dict_)
>> File 
>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>> 220, 
>> in execute
>> output = self.handle(*args, **options)
>> File 
>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>> 351, 
>> in handle
>>return self.handle_noargs(**options)
>> File 
>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>>  
>> line 52, in handle_noargs
>> cursor = connection.cursor()
>> File 
>> "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", 
>> line 
>> 15, in complain
>> raise ImproperlyConfigured("You hav
>> en't set the database ENGINE setting yet.")
>

Re: Django Improper Configuration

[Kimberly Harvey]

The directory I did it from was from my home directory. I've moved the files
like you've indicated by using mv settings.py settings.py.broken.

Should I go ahead and type in the command as python manage.py syncdb to see
if it works?

On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>>
>>
>>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST
>>
>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
>> settings.py is there.
>>
>
> Earlier you said you got:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   after importing setting
>   print settings.__file__
>   OUTPUT: settings.pyc
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   OUTPUT: wikicamp/settings.pyc
>
> What directory did you do that from.
>
> If you didn't run this from inside of site directory as was expecting and
> you did it from your home directory, then you have a settings.py sitting in
> your home directory which is the problem. Rename any settings.py file you
> home directory to something else.
>
>   mv ~/settings.py ~/settings.py.broken
>
> In short, you have more than one settings.py file somewhere where it is
> being found and the second one is causing a conflict.
>
> Graham
>
>
>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
>>
>>> Sorry about that, there is nothing showing for either  echo $PYTHONPATH
>>> and  echo $DJANGO_SETTINGS_MODULE
>>>
>>> I am currently reading your messages.
>>>
>>>
>>> On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
>>> graham.d...@gmail.com> wrote:
>>>


 On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>
> Please do the following and provide the output:
>
>   pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following, providing
> the output to us:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> after importing setting
> print settings.__file__
> OUTPUT: settings.pyc
>
>  import wikicamp.settings
>   print wikicamp.settings.__file__
>
> OUTPUT: wikicamp/settings.pyc
>

 Unfortunately you did not show what PYTHONPATH, or
 DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
 cause,
 but the above suggests that you have two Django projects created. One is 
 at:

   /home/username/wikicamp

 and the other at:

   /home/username/wikicamp/wikicamp

 Can you confirm this by indicating whether then file:

   /home/username/wikicamp/wikicamp/settings.py

 exists.

 If this is write, then what is happening is that when syncb is being
 running it is actually picking up the settings file from that second site
 nested within the first.

 If that is what has been done, then do:


   mv /home/username/wikicamp/wikicamp 
 /home/username/wikicamp/wikicamp.broken

 Also be aware that you shouldn't create Django apps with the same name
 as the project either, as the duplication of name can cause problems there
 as well, although for an app you wouldn't have a settings.py file in it,
 which in this case it seems you do.

 Graham


> These might produce exceptions depending on where you current working
> directory is.
>
> This is to show whether you may have created a backup copy of
> settings.py file somewhere which is being found instead of that in same
> directory as manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed
> it to.
>
>
>
> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton  > wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>>>
>>> Traceback ( most recent call last):
>>>  File "manage.py", line 11, in 
>>> execute_manager(settings)
>>> File "/usr/lib/python2.5/site-
>>> packages/django/core/management/_init_.py", line 438, in execute
>>> manager
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", 
>>> line
>>> 379, in execute
>>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>>> 191,
>>> in run_from_argv
>>> self.exectured(*args, **options._dict_)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>>> 220,
>>> in execute
>>> output = self.handle(*args, **options)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/manag

Re: Django Improper Configuration

[Kimberly Harvey]

I ran the syncdb and it says it doesn't recognize the wiki module. Also,
when I moved the original file which was settings.py to settings.py.broken,
that means I have to change the formats in the manage,py and other files so
that it recognizes the settings.py.broken file, right?

On Sun, Jan 23, 2011 at 11:25 PM, Kimberly Harvey wrote:

> The directory I did it from was from my home directory. I've moved the
> files like you've indicated by using mv settings.py settings.py.broken.
>
> Should I go ahead and type in the command as python manage.py syncdb to see
> if it works?
>
> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>>>
>>>
>>>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST
>>>
>>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
>>> settings.py is there.
>>>
>>
>> Earlier you said you got:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   after importing setting
>>   print settings.__file__
>>   OUTPUT: settings.pyc
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   OUTPUT: wikicamp/settings.pyc
>>
>> What directory did you do that from.
>>
>> If you didn't run this from inside of site directory as was expecting and
>> you did it from your home directory, then you have a settings.py sitting in
>> your home directory which is the problem. Rename any settings.py file you
>> home directory to something else.
>>
>>   mv ~/settings.py ~/settings.py.broken
>>
>> In short, you have more than one settings.py file somewhere where it is
>> being found and the second one is causing a conflict.
>>
>> Graham
>>
>>
>>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
>>>
  Sorry about that, there is nothing showing for either  echo $PYTHONPATH
 and  echo $DJANGO_SETTINGS_MODULE

 I am currently reading your messages.


 On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
 graham.d...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> MY OUTPUT: /home/username/wikicamp
>>
>> Now run 'python' from the command line and do the following, providing
>> the output to us:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> after importing setting
>> print settings.__file__
>> OUTPUT: settings.pyc
>>
>>  import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> OUTPUT: wikicamp/settings.pyc
>>
>
> Unfortunately you did not show what PYTHONPATH, or
> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
> cause,
> but the above suggests that you have two Django projects created. One is 
> at:
>
>   /home/username/wikicamp
>
> and the other at:
>
>   /home/username/wikicamp/wikicamp
>
> Can you confirm this by indicating whether then file:
>
>   /home/username/wikicamp/wikicamp/settings.py
>
> exists.
>
> If this is write, then what is happening is that when syncb is being
> running it is actually picking up the settings file from that second site
> nested within the first.
>
> If that is what has been done, then do:
>
>
>   mv /home/username/wikicamp/wikicamp 
> /home/username/wikicamp/wikicamp.broken
>
> Also be aware that you shouldn't create Django apps with the same name
> as the project either, as the duplication of name can cause problems there
> as well, although for an app you wouldn't have a settings.py file in it,
> which in this case it seems you do.
>
> Graham
>
>
>> These might produce exceptions depending on where you current working
>> directory is.
>>
>> This is to show whether you may have created a backup copy of
>> settings.py file somewhere which is being found instead of that in same
>> directory as manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed
>> it to.
>>
>>
>>
>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
>> graha...@gmail.com> wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:

 Traceback ( most recent call last):
  File "manage.py", line 11, in 
 execute_manager(settings)
 File "/usr/lib/python2.5/site-
 packages/django/core/management/_init_.py", line 438, in execute
 manager
 File
 "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", 
 line

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>
> The directory I did it from was from my home directory. I've moved the 
> files like you've indicated by using mv settings.py settings.py.broken.
>
> Should I go ahead and type in the command as python manage.py syncdb to see 
> if it works? 
>

YES. YES. YES.

:-)

Graham

 

>
> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>>>
>>>
>>>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST
>>>
>>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory, 
>>> settings.py is there.
>>>
>>
>> Earlier you said you got:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   after importing setting
>>   print settings.__file__
>>   OUTPUT: settings.pyc
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   OUTPUT: wikicamp/settings.pyc
>>
>> What directory did you do that from.
>>
>> If you didn't run this from inside of site directory as was expecting and 
>> you did it from your home directory, then you have a settings.py sitting in 
>> your home directory which is the problem. Rename any settings.py file you 
>> home directory to something else.
>>
>>   mv ~/settings.py ~/settings.py.broken
>>
>> In short, you have more than one settings.py file somewhere where it is 
>> being found and the second one is causing a conflict.
>>
>> Graham
>>  
>>
>>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
>>>
  Sorry about that, there is nothing showing for either  echo $PYTHONPATH 
 and  echo $DJANGO_SETTINGS_MODULE

 I am currently reading your messages.


 On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> MY OUTPUT: /home/username/wikicamp
>>
>> Now run 'python' from the command line and do the following, providing 
>> the output to us:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> after importing setting
>> print settings.__file__
>> OUTPUT: settings.pyc
>>
>>  import wikicamp.settings 
>>   print wikicamp.settings.__file__
>>
>> OUTPUT: wikicamp/settings.pyc
>>
>
> Unfortunately you did not show what PYTHONPATH, or 
> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
> cause, 
> but the above suggests that you have two Django projects created. One is 
> at:
>
>   /home/username/wikicamp
>
> and the other at:
>
>   /home/username/wikicamp/wikicamp
>
> Can you confirm this by indicating whether then file:
>
>   /home/username/wikicamp/wikicamp/settings.py
>
> exists.
>
> If this is write, then what is happening is that when syncb is being 
> running it is actually picking up the settings file from that second site 
> nested within the first.
>
> If that is what has been done, then do:
>
>
>   mv /home/username/wikicamp/wikicamp 
> /home/username/wikicamp/wikicamp.broken
>
> Also be aware that you shouldn't create Django apps with the same name 
> as the project either, as the duplication of name can cause problems 
> there 
> as well, although for an app you wouldn't have a settings.py file in it, 
> which in this case it seems you do.
>
> Graham
>  
>
>> These might produce exceptions depending on where you current working 
>> directory is.
>>
>> This is to show whether you may have created a backup copy of 
>> settings.py file somewhere which is being found instead of that in same 
>> directory as manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed 
>> it to.
>>
>>
>>
>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:

 Traceback ( most recent call last):
  File "manage.py", line 11, in 
 execute_manager(settings)
 File "/usr/lib/python2.5/site-
 packages/django/core/management/_init_.py", line 438, in execute 
 manager
 File 
 "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", 
 line 
 379, in execute
   self.fetch_command(subcommand).run_from_argv(self.argv)
 File 
 "/usr/lib/python2.5/site-packages/django/core/management/base.py", 
 line 191, 
 in run_from_argv
 self.exectured(*args, **options.

Re: Django Improper Configuration

[Kimberly Harvey]

Screen:

You just installed Django's auth system, which means you don't have any
superusers defined.

So it is working

I do have a question... after I've used the move technique to move the
settings.py settings.py.broken which places all of the file of settings.py
inside the settings.py.broken. I then MOVED the file again from
settings.py.broken to settings.py and at the command line, python manage.py
syncdb it works! May I ask why it worked like that?

On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>>
>> The directory I did it from was from my home directory. I've moved the
>> files like you've indicated by using mv settings.py settings.py.broken.
>>
>> Should I go ahead and type in the command as python manage.py syncdb to
>> see if it works?
>>
>
> YES. YES. YES.
>
> :-)
>
> Graham
>
>
>
>>
>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:


   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST

 WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
 settings.py is there.

>>>
>>> Earlier you said you got:
>>>
>>>   import settings
>>>   print settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   after importing setting
>>>   print settings.__file__
>>>   OUTPUT: settings.pyc
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   OUTPUT: wikicamp/settings.pyc
>>>
>>> What directory did you do that from.
>>>
>>> If you didn't run this from inside of site directory as was expecting and
>>> you did it from your home directory, then you have a settings.py sitting in
>>> your home directory which is the problem. Rename any settings.py file you
>>> home directory to something else.
>>>
>>>   mv ~/settings.py ~/settings.py.broken
>>>
>>> In short, you have more than one settings.py file somewhere where it is
>>> being found and the second one is causing a conflict.
>>>
>>> Graham
>>>
>>>
 On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:

>  Sorry about that, there is nothing showing for either  echo
> $PYTHONPATH and  echo $DJANGO_SETTINGS_MODULE
>
> I am currently reading your messages.
>
>
> On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton  > wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>>
>>> Please do the following and provide the output:
>>>
>>>   pwd
>>>
>>> MY OUTPUT: /home/username/wikicamp
>>>
>>> Now run 'python' from the command line and do the following,
>>> providing the output to us:
>>>
>>>   import settings
>>>   print settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> after importing setting
>>> print settings.__file__
>>> OUTPUT: settings.pyc
>>>
>>>  import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> OUTPUT: wikicamp/settings.pyc
>>>
>>
>> Unfortunately you did not show what PYTHONPATH, or
>> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
>> cause,
>> but the above suggests that you have two Django projects created. One is 
>> at:
>>
>>   /home/username/wikicamp
>>
>> and the other at:
>>
>>   /home/username/wikicamp/wikicamp
>>
>> Can you confirm this by indicating whether then file:
>>
>>   /home/username/wikicamp/wikicamp/settings.py
>>
>> exists.
>>
>> If this is write, then what is happening is that when syncb is being
>> running it is actually picking up the settings file from that second site
>> nested within the first.
>>
>> If that is what has been done, then do:
>>
>>
>>   mv /home/username/wikicamp/wikicamp 
>> /home/username/wikicamp/wikicamp.broken
>>
>> Also be aware that you shouldn't create Django apps with the same name
>> as the project either, as the duplication of name can cause problems 
>> there
>> as well, although for an app you wouldn't have a settings.py file in it,
>> which in this case it seems you do.
>>
>> Graham
>>
>>
>>> These might produce exceptions depending on where you current working
>>> directory is.
>>>
>>> This is to show whether you may have created a backup copy of
>>> settings.py file somewhere which is being found instead of that in same
>>> directory as manage.py.
>>>
>>> Finally, if you have modified manage.py, tell is what you have
>>> changed it to.
>>>
>>>
>>>
>>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
>>> grah...@gmail.com> wrote:
>>>


 On Monday, January 24, 

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 4:39:47 PM UTC+11, Kimberly wrote:
>
> Screen:
>
> You just installed Django's auth system, which means you don't have any 
> superusers defined.
>
> So it is working
>
> I do have a question... after I've used the move technique to move the 
> settings.py settings.py.broken which places all of the file of settings.py 
> inside the settings.py.broken. I then MOVED the file again from 
> settings.py.broken to settings.py and at the command line, python manage.py 
> syncdb it works! May I ask why it worked like that?
>

No idea. Just don't put any backup copy of settings.py in the directory 
above where the proper one is located. This is because Django does a trick 
with the Python module search path so that that parent directory gets added 
to sys.path for a moment and this may cause that backup copy to get imported 
wrongly meaning wrong settings used. So, don't question it, just be happy it 
is working. :-)

Graham

 

> On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>>>
>>> The directory I did it from was from my home directory. I've moved the 
>>> files like you've indicated by using mv settings.py settings.py.broken.
>>>
>>> Should I go ahead and type in the command as python manage.py syncdb to 
>>> see if it works? 
>>>
>>
>> YES. YES. YES.
>>
>> :-)
>>
>> Graham
>>
>>  
>>
>>>
>>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton 
>>> wrote:
>>>
  

 On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>
>
>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT EXIST
>
> WHAT DOES EXIST: /home/username/wikicamp and inside that directory, 
> settings.py is there.
>

 Earlier you said you got:

   import settings
   print settings.__file__

   import wikicamp.settings
   print wikicamp.settings.__file__

   after importing setting
   print settings.__file__
   OUTPUT: settings.pyc

   import wikicamp.settings
   print wikicamp.settings.__file__

   OUTPUT: wikicamp/settings.pyc

 What directory did you do that from.

 If you didn't run this from inside of site directory as was expecting 
 and you did it from your home directory, then you have a settings.py 
 sitting 
 in your home directory which is the problem. Rename any settings.py file 
 you 
 home directory to something else.

   mv ~/settings.py ~/settings.py.broken

 In short, you have more than one settings.py file somewhere where it is 
 being found and the second one is causing a conflict.

 Graham
  

>  On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey 
> wrote:
>
>>  Sorry about that, there is nothing showing for either  echo 
>> $PYTHONPATH and  echo $DJANGO_SETTINGS_MODULE
>>
>> I am currently reading your messages.
>>
>>
>>  On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
>> grah...@gmail.com> wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:

 Please do the following and provide the output:

   pwd

 MY OUTPUT: /home/username/wikicamp

 Now run 'python' from the command line and do the following, 
 providing the output to us:

   import settings
   print settings.__file__

   import wikicamp.settings
   print wikicamp.settings.__file__

 after importing setting
 print settings.__file__
 OUTPUT: settings.pyc

  import wikicamp.settings 
   print wikicamp.settings.__file__

 OUTPUT: wikicamp/settings.pyc

>>>
>>> Unfortunately you did not show what PYTHONPATH, or 
>>> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
>>> cause, 
>>> but the above suggests that you have two Django projects created. One 
>>> is at:
>>>
>>>   /home/username/wikicamp
>>>
>>> and the other at:
>>>
>>>   /home/username/wikicamp/wikicamp
>>>
>>> Can you confirm this by indicating whether then file:
>>>
>>>   /home/username/wikicamp/wikicamp/settings.py
>>>
>>> exists.
>>>
>>> If this is write, then what is happening is that when syncb is being 
>>> running it is actually picking up the settings file from that second 
>>> site 
>>> nested within the first.
>>>
>>> If that is what has been done, then do:
>>>
>>>
>>>   mv /home/username/wikicamp/wikicamp 
>>> /home/username/wikicamp/wikicamp.broken
>>>
>>> Also be aware that you shouldn't create Django apps with the same 
>>> name as the project either, as the duplication of name can cause 
>>> problems 
>>> there as well, although for an app

Re: Django Improper Configuration

[Kimberly Harvey]

LOL, I do have another thing I want to ask. I ran the server ( 0 errors) but
when to the browser to check,  http://127.0.0.1:8000/ and now it says it
refused the connection. It said that the server may be busy or may have
network connection problem. It also said I may have an old version of the
page I wanted
1) Google cache
2) Internet Archive

Please tell me that it has nothing to do with the settings, manage, urls,
etc files. Do I need to change my cache as it may be the problem?

As for the question about the settings.py, and settings.py.broken, I won't
question it, lol.

On Sun, Jan 23, 2011 at 11:50 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 4:39:47 PM UTC+11, Kimberly wrote:
>>
>> Screen:
>>
>> You just installed Django's auth system, which means you don't have any
>> superusers defined.
>>
>> So it is working
>>
>> I do have a question... after I've used the move technique to move the
>> settings.py settings.py.broken which places all of the file of settings.py
>> inside the settings.py.broken. I then MOVED the file again from
>> settings.py.broken to settings.py and at the command line, python manage.py
>> syncdb it works! May I ask why it worked like that?
>>
>
> No idea. Just don't put any backup copy of settings.py in the directory
> above where the proper one is located. This is because Django does a trick
> with the Python module search path so that that parent directory gets added
> to sys.path for a moment and this may cause that backup copy to get imported
> wrongly meaning wrong settings used. So, don't question it, just be happy it
> is working. :-)
>
> Graham
>
>
>
>> On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:

 The directory I did it from was from my home directory. I've moved the
 files like you've indicated by using mv settings.py settings.py.broken.

 Should I go ahead and type in the command as python manage.py syncdb to
 see if it works?

>>>
>>> YES. YES. YES.
>>>
>>> :-)
>>>
>>> Graham
>>>
>>>
>>>

 On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>>
>>
>>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT
>> EXIST
>>
>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
>> settings.py is there.
>>
>
> Earlier you said you got:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   after importing setting
>   print settings.__file__
>   OUTPUT: settings.pyc
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   OUTPUT: wikicamp/settings.pyc
>
> What directory did you do that from.
>
> If you didn't run this from inside of site directory as was expecting
> and you did it from your home directory, then you have a settings.py 
> sitting
> in your home directory which is the problem. Rename any settings.py file 
> you
> home directory to something else.
>
>   mv ~/settings.py ~/settings.py.broken
>
> In short, you have more than one settings.py file somewhere where it is
> being found and the second one is causing a conflict.
>
> Graham
>
>
>>  On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey 
>> wrote:
>>
>>>  Sorry about that, there is nothing showing for either  echo
>>> $PYTHONPATH and  echo $DJANGO_SETTINGS_MODULE
>>>
>>> I am currently reading your messages.
>>>
>>>
>>>  On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
>>> grah...@gmail.com> wrote:
>>>


 On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>
> Please do the following and provide the output:
>
>   pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following,
> providing the output to us:
>
>   import settings
>   print settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> after importing setting
> print settings.__file__
> OUTPUT: settings.pyc
>
>  import wikicamp.settings
>   print wikicamp.settings.__file__
>
> OUTPUT: wikicamp/settings.pyc
>

 Unfortunately you did not show what PYTHONPATH, or
 DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
 cause,
 but the above suggests that you have two Django projects created. One 
 is at:

   /home/username/wikicamp

 and the other a

Re: Django Improper Configuration

[Graham Dumpleton]

On Monday, January 24, 2011 5:05:05 PM UTC+11, Kimberly wrote:
>
> LOL, I do have another thing I want to ask. I ran the server ( 0 errors) 
> but when to the browser to check,  http://127.0.0.1:8000/ and now it says 
> it refused the connection. It said that the server may be busy or may have 
> network connection problem. It also said I may have an old version of the 
> page I wanted
> 1) Google cache
> 2) Internet Archive
>

If you have a new problem and can't work out out, I would strongly suggest 
you create a new distinct message thread so that it isn't buried in this 
one. This one has gone on so long that people would now be ignoring it most 
likely. Use a new thread for new issue and you will have more luck getting 
help with it. More than likely your issue is transient and will resolve 
itself. Am sure someone else will help if they are able. I am taking a break 
for a while.

Graham
 

> Please tell me that it has nothing to do with the settings, manage, urls, 
> etc files. Do I need to change my cache as it may be the problem? 
>
> As for the question about the settings.py, and settings.py.broken, I won't 
> question it, lol.
>
> On Sun, Jan 23, 2011 at 11:50 PM, Graham Dumpleton 
> wrote:
>
>>
>>
>> On Monday, January 24, 2011 4:39:47 PM UTC+11, Kimberly wrote:
>>>
>>> Screen:
>>>
>>> You just installed Django's auth system, which means you don't have any 
>>> superusers defined.
>>>
>>> So it is working
>>>
>>> I do have a question... after I've used the move technique to move the 
>>> settings.py settings.py.broken which places all of the file of settings.py 
>>> inside the settings.py.broken. I then MOVED the file again from 
>>> settings.py.broken to settings.py and at the command line, python manage.py 
>>> syncdb it works! May I ask why it worked like that?
>>>
>>
>> No idea. Just don't put any backup copy of settings.py in the directory 
>> above where the proper one is located. This is because Django does a trick 
>> with the Python module search path so that that parent directory gets added 
>> to sys.path for a moment and this may cause that backup copy to get imported 
>> wrongly meaning wrong settings used. So, don't question it, just be happy it 
>> is working. :-)
>>
>> Graham
>>
>>  
>>
>>> On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton 
>>> wrote:
>>>
  

 On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>
> The directory I did it from was from my home directory. I've moved the 
> files like you've indicated by using mv settings.py settings.py.broken.
>
> Should I go ahead and type in the command as python manage.py syncdb to 
> see if it works? 
>

 YES. YES. YES.

 :-)

 Graham

  

>
> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton 
> wrote:
>
>>  
>>
>> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>>>
>>>
>>>   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT 
>>> EXIST
>>>
>>> WHAT DOES EXIST: /home/username/wikicamp and inside that directory, 
>>> settings.py is there.
>>>
>>
>> Earlier you said you got:
>>
>>   import settings
>>   print settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   after importing setting
>>   print settings.__file__
>>   OUTPUT: settings.pyc
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   OUTPUT: wikicamp/settings.pyc
>>
>> What directory did you do that from.
>>
>> If you didn't run this from inside of site directory as was expecting 
>> and you did it from your home directory, then you have a settings.py 
>> sitting 
>> in your home directory which is the problem. Rename any settings.py file 
>> you 
>> home directory to something else.
>>
>>   mv ~/settings.py ~/settings.py.broken
>>
>> In short, you have more than one settings.py file somewhere where it 
>> is being found and the second one is causing a conflict.
>>
>> Graham
>>  
>>
>>>  On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey >> > wrote:
>>>
   Sorry about that, there is nothing showing for either  echo 
 $PYTHONPATH and  echo $DJANGO_SETTINGS_MODULE

 I am currently reading your messages.


  On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
 gra...@gmail.com> wrote:

>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> MY OUTPUT: /home/username/wikicamp
>>
>> Now run 'python' from the command line and do the following, 
>> providing the output to us:
>>
>>   import settings
>>   p

Re: Django Improper Configuration

[Kimberly Harvey]

Thanks for the advice. Thanks for your help!

On Mon, Jan 24, 2011 at 12:10 AM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
> our help
> On Monday, January 24, 2011 5:05:05 PM UTC+11, Kimberly wrote:
>>
>> LOL, I do have another thing I want to ask. I ran the server ( 0 errors)
>> but when to the browser to check,  http://127.0.0.1:8000/ and now it says
>> it refused the connection. It said that the server may be busy or may have
>> network connection problem. It also said I may have an old version of the
>> page I wanted
>> 1) Google cache
>> 2) Internet Archive
>>
>
> If you have a new problem and can't work out out, I would strongly suggest
> you create a new distinct message thread so that it isn't buried in this
> one. This one has gone on so long that people would now be ignoring it most
> likely. Use a new thread for new issue and you will have more luck getting
> help with it. More than likely your issue is transient and will resolve
> itself. Am sure someone else will help if they are able. I am taking a break
> for a while.
>
> Graham
>
>
>> Please tell me that it has nothing to do with the settings, manage, urls,
>> etc files. Do I need to change my cache as it may be the problem?
>>
>> As for the question about the settings.py, and settings.py.broken, I won't
>> question it, lol.
>>
>> On Sun, Jan 23, 2011 at 11:50 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 4:39:47 PM UTC+11, Kimberly wrote:

 Screen:

 You just installed Django's auth system, which means you don't have any
 superusers defined.

 So it is working

 I do have a question... after I've used the move technique to move the
 settings.py settings.py.broken which places all of the file of settings.py
 inside the settings.py.broken. I then MOVED the file again from
 settings.py.broken to settings.py and at the command line, python manage.py
 syncdb it works! May I ask why it worked like that?

>>>
>>> No idea. Just don't put any backup copy of settings.py in the directory
>>> above where the proper one is located. This is because Django does a trick
>>> with the Python module search path so that that parent directory gets added
>>> to sys.path for a moment and this may cause that backup copy to get imported
>>> wrongly meaning wrong settings used. So, don't question it, just be happy it
>>> is working. :-)
>>>
>>> Graham
>>>
>>>
>>>
 On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton 
 wrote:

>
>
> On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>>
>> The directory I did it from was from my home directory. I've moved the
>> files like you've indicated by using mv settings.py settings.py.broken.
>>
>> Should I go ahead and type in the command as python manage.py syncdb
>> to see if it works?
>>
>
> YES. YES. YES.
>
> :-)
>
> Graham
>
>
>
>>
>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:


   /home/username/wikicamp/wikicamp/settings.py -->  THIS DOES NOT
 EXIST

 WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
 settings.py is there.

>>>
>>> Earlier you said you got:
>>>
>>>   import settings
>>>   print settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   after importing setting
>>>   print settings.__file__
>>>   OUTPUT: settings.pyc
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   OUTPUT: wikicamp/settings.pyc
>>>
>>> What directory did you do that from.
>>>
>>> If you didn't run this from inside of site directory as was expecting
>>> and you did it from your home directory, then you have a settings.py 
>>> sitting
>>> in your home directory which is the problem. Rename any settings.py 
>>> file you
>>> home directory to something else.
>>>
>>>   mv ~/settings.py ~/settings.py.broken
>>>
>>> In short, you have more than one settings.py file somewhere where it
>>> is being found and the second one is causing a conflict.
>>>
>>> Graham
>>>
>>>
  On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey <
 kha...@gmail.com> wrote:

>   Sorry about that, there is nothing showing for either  echo
> $PYTHONPATH and  echo $DJANGO_SETTINGS_MODULE
>
> I am currently reading your messages.
>
>
>  On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
> gra...@gmail.com> wrote:
>
>>
>>
>> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>>>
>>> Please do the following and pro

Re: Django Improper Configuration

[Kelly Nicholes]

I think I had this error too when I was cloning a repo from WebFaction
to use on my local dev machine.  I ended up having to replace
WebFaction's manage.py with the one from Django.  Let me know if it
works for you!  I wish I could explain why.  Can't.

On Jan 23, 8:55 pm, Graham Dumpleton 
wrote:
> Are you saying that those two print statements you were told to add are not
> causing anything additional to be displayed on the screen when you run both
> runserver and syncdb?
>
> This is why I asked you to provide the output again. You may not understand
> what we are looking for. Don't care about what the error is at the point but
> the information that those print statements should have output.
>
> Graham
>
>
>
>
>
>
>
> On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>
> > I've provided the full errors in the post, it is there. ( same errors as
> > I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as
> > I'm encountering the same after I've copied and paste the print inside the
> > settings.py file at the end)
>
> > On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton 
> > wrote:
>
> >> That is two underscores, followed by 'file' followed by two underscores.
> >> Not just a single underscore.
>
> >> Please try and cut and paste out we give to use and vice versa. In other
> >> words, provide complete output showing full errors and tracebacks. Such
> >> information may be meaningful to use even if you think it isn't.
>
> >> Graham
>
> >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>
> >>> it says that the _file_ is not defined.
>
> >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
> >>> wrote:
>
>  On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>
> > Copy and Paste the following to replace your entire DATABASES tuple:
>
> > DATABASES = {
> >     'default': {
> >         'ENGINE': 'django.db.backends.sqlite3',
> >         'NAME': 'database.db',                    
> >         'USER': '',                      
> >         'PASSWORD': '',                  
> >         'HOST': '',                      
> >         'PORT': '',                      
> >     }
> > }
>
> > it looks like in your configuration you are also missing a comma after
> > the name of the database. Remember you must include that comma because 
> > this
> > is a tuple.
>
>  That was already pointed out to them.
>
>  The lack of a comma should have resulted in a syntax error, which makes
>  me believe, unless they modified the content before posting, that they 
>  may
>  be modifying a different file to what is being read.
>
>  I would like to see them, instead of changing DATABASES yet again, is to
>  add at the very end of their settings.py file, the lines:
>
>    print __file__
>    print 'DATABASES', DATABASES
>
>  This will prove two things. First that the file is being read as the
>  output from this should show on stdout when running runserver or syncdb.
>  Second, will show what Python is seeing DATABASES as being set to.
>
>  if it doesn't show, then wrong file. If shows, but is different to what
>  they believe they are setting it to, they could have multiple DATABASES
>  entries in file.
>
>  Graham
>
>   --
>  You received this message because you are subscribed to the Google
>  Groups "Django users" group.
>  To post to this group, send email to djan...@googlegroups.com.
>  To unsubscribe from this group, send email to
>  django-...@googlegroups.com.
>
>  For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
> >>>  --
> >> You received this message because you are subscribed to the Google Groups
> >> "Django users" group.
> >> To post to this group, send email to django...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> django-users...@googlegroups.com.
> >> For more options, visit this group at
> >>http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Mark Penix]

This might be a stupid question but did you install the sqlite package?

On Mon, Jan 24, 2011 at 9:39 AM, Kelly Nicholes wrote:

> I think I had this error too when I was cloning a repo from WebFaction
> to use on my local dev machine.  I ended up having to replace
> WebFaction's manage.py with the one from Django.  Let me know if it
> works for you!  I wish I could explain why.  Can't.
>
> On Jan 23, 8:55 pm, Graham Dumpleton 
> wrote:
>  > Are you saying that those two print statements you were told to add are
> not
> > causing anything additional to be displayed on the screen when you run
> both
> > runserver and syncdb?
> >
> > This is why I asked you to provide the output again. You may not
> understand
> > what we are looking for. Don't care about what the error is at the point
> but
> > the information that those print statements should have output.
> >
> > Graham
> >
> >
> >
> >
> >
> >
> >
> > On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
> >
> > > I've provided the full errors in the post, it is there. ( same errors
> as
> > > I've faced prior to adding the print __file__ and 'DATABASES',
> DATABASES) as
> > > I'm encountering the same after I've copied and paste the print inside
> the
> > > settings.py file at the end)
> >
> > > On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton <
> graham.d...@gmail.com>wrote:
> >
> > >> That is two underscores, followed by 'file' followed by two
> underscores.
> > >> Not just a single underscore.
> >
> > >> Please try and cut and paste out we give to use and vice versa. In
> other
> > >> words, provide complete output showing full errors and tracebacks.
> Such
> > >> information may be meaningful to use even if you think it isn't.
> >
> > >> Graham
> >
> > >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
> >
> > >>> it says that the _file_ is not defined.
> >
> > >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
> graha...@gmail.com>wrote:
> >
> >  On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr
> wrote:
> >
> > > Copy and Paste the following to replace your entire DATABASES
> tuple:
> >
> > > DATABASES = {
> > > 'default': {
> > > 'ENGINE': 'django.db.backends.sqlite3',
> > > 'NAME': 'database.db',
> > > 'USER': '',
> > > 'PASSWORD': '',
> > > 'HOST': '',
> > > 'PORT': '',
> > > }
> > > }
> >
> > > it looks like in your configuration you are also missing a comma
> after
> > > the name of the database. Remember you must include that comma
> because this
> > > is a tuple.
> >
> >  That was already pointed out to them.
> >
> >  The lack of a comma should have resulted in a syntax error, which
> makes
> >  me believe, unless they modified the content before posting, that
> they may
> >  be modifying a different file to what is being read.
> >
> >  I would like to see them, instead of changing DATABASES yet again,
> is to
> >  add at the very end of their settings.py file, the lines:
> >
> >    print __file__
> >    print 'DATABASES', DATABASES
> >
> >  This will prove two things. First that the file is being read as the
> >  output from this should show on stdout when running runserver or
> syncdb.
> >  Second, will show what Python is seeing DATABASES as being set to.
> >
> >  if it doesn't show, then wrong file. If shows, but is different to
> what
> >  they believe they are setting it to, they could have multiple
> DATABASES
> >  entries in file.
> >
> >  Graham
> >
> >   --
> >  You received this message because you are subscribed to the Google
> >  Groups "Django users" group.
> >  To post to this group, send email to djan...@googlegroups.com.
> >  To unsubscribe from this group, send email to
> >  django-...@googlegroups.com.
> >
> >  For more options, visit this group at
> > http://groups.google.com/group/django-users?hl=en.
> >
> > >>>  --
> > >> You received this message because you are subscribed to the Google
> Groups
> > >> "Django users" group.
> > >> To post to this group, send email to django...@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> django-users...@googlegroups.com.
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/django-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>


-- 
*Mark Penix*
*Independent Team Beachbody Fitness Coach*
http://www.markpenix.com
http://www.beachbodycoach.com/MarkP90X
http://www.myshakeology.com/MarkP90X
*402-321-8996*

-- 
You received this

Re: Django Improper Configuration

[Kimberly Harvey]

Karen,

  It worked after I used the mv command to move the settings.py
settings.py.break and then did another move where from settings.py.break to
settings.py, then I ran the server by using the manage.py syncdb. I do not
understand why that even worked ( I didn't want to use the settings.py.break
because the Django originally used the settings.py), so that why I did the
move 2 times. Originally before the settings.py.break came into play, there
was another settings.py elsewhere in the file which create some corruption (
hence, problem with configuration -- DATABASE ENGINE was not set).
Therefore, to remove the settings.py from another location, I had to do what
I did above. Oddly, it works.

On Mon, Jan 24, 2011 at 12:29 PM, Mark Penix  wrote:

> This might be a stupid question but did you install the sqlite package?
>
>
> On Mon, Jan 24, 2011 at 9:39 AM, Kelly Nicholes wrote:
>
>> I think I had this error too when I was cloning a repo from WebFaction
>> to use on my local dev machine.  I ended up having to replace
>> WebFaction's manage.py with the one from Django.  Let me know if it
>> works for you!  I wish I could explain why.  Can't.
>>
>> On Jan 23, 8:55 pm, Graham Dumpleton 
>> wrote:
>>  > Are you saying that those two print statements you were told to add
>> are not
>> > causing anything additional to be displayed on the screen when you run
>> both
>> > runserver and syncdb?
>> >
>> > This is why I asked you to provide the output again. You may not
>> understand
>> > what we are looking for. Don't care about what the error is at the point
>> but
>> > the information that those print statements should have output.
>> >
>> > Graham
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>> >
>> > > I've provided the full errors in the post, it is there. ( same errors
>> as
>> > > I've faced prior to adding the print __file__ and 'DATABASES',
>> DATABASES) as
>> > > I'm encountering the same after I've copied and paste the print inside
>> the
>> > > settings.py file at the end)
>> >
>> > > On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton <
>> graham.d...@gmail.com>wrote:
>> >
>> > >> That is two underscores, followed by 'file' followed by two
>> underscores.
>> > >> Not just a single underscore.
>> >
>> > >> Please try and cut and paste out we give to use and vice versa. In
>> other
>> > >> words, provide complete output showing full errors and tracebacks.
>> Such
>> > >> information may be meaningful to use even if you think it isn't.
>> >
>> > >> Graham
>> >
>> > >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>> >
>> > >>> it says that the _file_ is not defined.
>> >
>> > >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
>> graha...@gmail.com>wrote:
>> >
>> >  On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr
>> wrote:
>> >
>> > > Copy and Paste the following to replace your entire DATABASES
>> tuple:
>> >
>> > > DATABASES = {
>> > > 'default': {
>> > > 'ENGINE': 'django.db.backends.sqlite3',
>> > > 'NAME': 'database.db',
>> > > 'USER': '',
>> > > 'PASSWORD': '',
>> > > 'HOST': '',
>> > > 'PORT': '',
>> > > }
>> > > }
>> >
>> > > it looks like in your configuration you are also missing a comma
>> after
>> > > the name of the database. Remember you must include that comma
>> because this
>> > > is a tuple.
>> >
>> >  That was already pointed out to them.
>> >
>> >  The lack of a comma should have resulted in a syntax error, which
>> makes
>> >  me believe, unless they modified the content before posting, that
>> they may
>> >  be modifying a different file to what is being read.
>> >
>> >  I would like to see them, instead of changing DATABASES yet again,
>> is to
>> >  add at the very end of their settings.py file, the lines:
>> >
>> >    print __file__
>> >    print 'DATABASES', DATABASES
>> >
>> >  This will prove two things. First that the file is being read as
>> the
>> >  output from this should show on stdout when running runserver or
>> syncdb.
>> >  Second, will show what Python is seeing DATABASES as being set to.
>> >
>> >  if it doesn't show, then wrong file. If shows, but is different to
>> what
>> >  they believe they are setting it to, they could have multiple
>> DATABASES
>> >  entries in file.
>> >
>> >  Graham
>> >
>> >   --
>> >  You received this message because you are subscribed to the Google
>> >  Groups "Django users" group.
>> >  To post to this group, send email to djan...@googlegroups.com.
>> >  To unsubscribe from this group, send email to
>> >  django-...@googlegroups.com.
>> >
>> >  For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> > >>>  --
>> > >> You received this message because you are subscribed to the Google
>> Grou

Re: Django Improper Configuration

[Kimberly Harvey]

yes the sqlite package is installed. I installed the Django and the python,
and I test it to ensure it is there and it is.

On Mon, Jan 24, 2011 at 12:48 PM, Kimberly Harvey wrote:

> Karen,
>
>   It worked after I used the mv command to move the settings.py
> settings.py.break and then did another move where from settings.py.break to
> settings.py, then I ran the server by using the manage.py syncdb. I do not
> understand why that even worked ( I didn't want to use the settings.py.break
> because the Django originally used the settings.py), so that why I did the
> move 2 times. Originally before the settings.py.break came into play, there
> was another settings.py elsewhere in the file which create some corruption (
> hence, problem with configuration -- DATABASE ENGINE was not set).
> Therefore, to remove the settings.py from another location, I had to do what
> I did above. Oddly, it works.
>
> On Mon, Jan 24, 2011 at 12:29 PM, Mark Penix  wrote:
>
>> This might be a stupid question but did you install the sqlite package?
>>
>>
>> On Mon, Jan 24, 2011 at 9:39 AM, Kelly Nicholes 
>> wrote:
>>
>>> I think I had this error too when I was cloning a repo from WebFaction
>>> to use on my local dev machine.  I ended up having to replace
>>> WebFaction's manage.py with the one from Django.  Let me know if it
>>> works for you!  I wish I could explain why.  Can't.
>>>
>>> On Jan 23, 8:55 pm, Graham Dumpleton 
>>> wrote:
>>>  > Are you saying that those two print statements you were told to add
>>> are not
>>> > causing anything additional to be displayed on the screen when you run
>>> both
>>> > runserver and syncdb?
>>> >
>>> > This is why I asked you to provide the output again. You may not
>>> understand
>>> > what we are looking for. Don't care about what the error is at the
>>> point but
>>> > the information that those print statements should have output.
>>> >
>>> > Graham
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>>> >
>>> > > I've provided the full errors in the post, it is there. ( same errors
>>> as
>>> > > I've faced prior to adding the print __file__ and 'DATABASES',
>>> DATABASES) as
>>> > > I'm encountering the same after I've copied and paste the print
>>> inside the
>>> > > settings.py file at the end)
>>> >
>>> > > On Sun, Jan 23, 2011 at 9:40 PM, Graham Dumpleton <
>>> graham.d...@gmail.com>wrote:
>>> >
>>> > >> That is two underscores, followed by 'file' followed by two
>>> underscores.
>>> > >> Not just a single underscore.
>>> >
>>> > >> Please try and cut and paste out we give to use and vice versa. In
>>> other
>>> > >> words, provide complete output showing full errors and tracebacks.
>>> Such
>>> > >> information may be meaningful to use even if you think it isn't.
>>> >
>>> > >> Graham
>>> >
>>> > >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>> >
>>> > >>> it says that the _file_ is not defined.
>>> >
>>> > >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
>>> graha...@gmail.com>wrote:
>>> >
>>> >  On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr
>>> wrote:
>>> >
>>> > > Copy and Paste the following to replace your entire DATABASES
>>> tuple:
>>> >
>>> > > DATABASES = {
>>> > > 'default': {
>>> > > 'ENGINE': 'django.db.backends.sqlite3',
>>> > > 'NAME': 'database.db',
>>> > > 'USER': '',
>>> > > 'PASSWORD': '',
>>> > > 'HOST': '',
>>> > > 'PORT': '',
>>> > > }
>>> > > }
>>> >
>>> > > it looks like in your configuration you are also missing a comma
>>> after
>>> > > the name of the database. Remember you must include that comma
>>> because this
>>> > > is a tuple.
>>> >
>>> >  That was already pointed out to them.
>>> >
>>> >  The lack of a comma should have resulted in a syntax error, which
>>> makes
>>> >  me believe, unless they modified the content before posting, that
>>> they may
>>> >  be modifying a different file to what is being read.
>>> >
>>> >  I would like to see them, instead of changing DATABASES yet again,
>>> is to
>>> >  add at the very end of their settings.py file, the lines:
>>> >
>>> >    print __file__
>>> >    print 'DATABASES', DATABASES
>>> >
>>> >  This will prove two things. First that the file is being read as
>>> the
>>> >  output from this should show on stdout when running runserver or
>>> syncdb.
>>> >  Second, will show what Python is seeing DATABASES as being set to.
>>> >
>>> >  if it doesn't show, then wrong file. If shows, but is different to
>>> what
>>> >  they believe they are setting it to, they could have multiple
>>> DATABASES
>>> >  entries in file.
>>> >
>>> >  Graham
>>> >
>>> >   --
>>> >  You received this message because you are subscribed to the Google
>>> >  Groups "Django users" group.
>>> >  To post to this group, send email to d