Malcolm Tredinnick wrote:
<snip>
> That should be easy enough to diagnose. My initial guess would be that
> bbg is in django_projects/, rather than django_src/, just from the way
> you named your directories. Remember that .bash_profile is obviously not
> going to be run by Apache (it's not bash, after all) and your PYTHONPATH
> settings there were broader than your mod_python config settings.
Hrm. bbg is my project and it is in django_projects/ . The tutorial
suggests you can stick your project directory anywhere you like, with
the caveat of staying out of docroot. That suggests that I've done
something silly with the httpd.conf. PYTHONPATH has to include
/django_src. And I just realized I don't ever see where
/django_projects is made known to the server, which must be what you
mean by "broader than your mod_python config settings." So, let me
toddle off and try to change that.
>
> >
> > I'll investigate on my own, but thanks for editorial wizardry! :)
> >
> > re: import django: Yes, it returns literally nothing. I was trying to
> > establish that I could load django in the shell at least.
> >
> > The bbg/urls.py looks like this:
> > urlpatterns = patterns('',
> > ( r'^admin/' , include( 'django.contrib.admin.urls' ) ) ,
> > ( r'' , include( 'bbg.goods' ) ) ,
> > )
> >
> > I was trying to tie /bbg to the top level. Is there a better, official
> > way to do this?
>
> I have many questions at this point. Firstly, is it correct to assume
> your project is called bbg/ ? So bbg.urls is the value of the
> ROOT_URLCONF setting in your appropriate settings.py?
Yes, /bbg is project. ROOT_URLCONF = 'bbg.urls', yes.
> If so, the "include ('bbg.goods')" line looks suspicious. Is "goods.py"
> a URL configuration file? Or did you mean that to be bbg.goods.url?
Huh. I was following the example in the tutorial, so while I *thought*
I meant to use bbg.goods, it may very well be I was mistaken. Tutorial
shows:
<quote>
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'mysite.polls'
)
</quote>
> The previous error you posted was saying there was something wrong with
> the construction of your root URL conf (bbg/urls.py, presumably), so
> investigate that file carefully. For example, comment out both lines:
> does runserver start? Can you view http://localhost:8000/ (it will give
> you a pretty error page)? No uncomment the admin line. Rinse, wash,
> repeat.
Commenting both out netted me the "Congrats, it worked" page. Re-adding
the admin spit a 404 back for / and the admin login for /admin.
Commenting admin out and re-adding bbg gives me the same AttributeError
exception. Interestingly, /admin still shows a login, although when I
log in, it dumps the same AttributeError exception.
Once again, thanks for your help!
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
