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 <mark.pe...@gmail.com> 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 <kelbolici...@gmail.com>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 <graham.dumple...@gmail.com> >> 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<django-users%2bunsubscr...@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://goog_1120260081/>http://www.markpenix.com > http://www.beachbodycoach.com/MarkP90X > http://www.myshakeology.com/MarkP90X > *402-321-8996* > > -- > 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.