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 <kharve...@gmail.com>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 <khar...@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 <
>>>> 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 <module>
>>>>>>>> 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 <
>>>>>>>> grah...@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 <module>
>>>>>>>>> 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 <
>>>>>>>>>>> gra...@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 <
>>>>>>>>>>>>> gra...@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 dja...@googlegroups.com.
>>>>>>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>>>>>>> dja...@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 dja...@googlegroups.com.
>>>>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>>>>> djan...@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 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/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<django-users%2bunsubscr...@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.
