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 <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 <graham.d...@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...@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.
