On Thu, Apr 2, 2009 at 1:15 PM, laird18 <michael.hopcr...@gmail.com> wrote:

>
> Hi Karen, thanks for the reply, and sorry for not being clearer in my
> original message.
>
> I've done a bit more debugging and I've found that whenever I put any
> form of import line, such as
> "from django.db import models" or
> "from internal.models import *" in __init__.py I get the following
> error when running syncdb:
>

Why are you even running syncdb after making these changes to __init__.py?
(And for that matter, which __init__.py file, specifically, are you adding
these to?)  syncdb is used to create database tables -- changes to an
__init__.py don't require re-running syncdb.  But if syncdb is giving an
error here then any use of manage.py is going to give the same error because
importing settings is done for all of them.


>
> "Error: Can't find the file 'settings.py' in the directory containing
> '/home/mhop/django/mopan/manage.py'. It appears you've customized
> things.
> You'll have to run django-admin.py, passing it your settings module.
> (If the file settings.py does indeed exist, it's causing an
> ImportError somehow.)"
>

I'll assume you've ensured the obvious cause isn't to blame here, and that
you do in fact have your settings.py file in the same directory as
manage.py.  So what you need to figure out is why 'import settings' in
manage.py is raising an ImportError.  Easiest way to do that is likely to
just try 'import settings' from an interactive python session run from the
root of your project tree and see what message goes with the ImportError
that throws.

Karen

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to