Crapola. r6718 was a patch I wrote. Without the patch you only get app-defined commands if you use manage.py. With django-admin.py, you don't get app-defined commands, even if you specify a --settings=path module.
I just tried the steps you mentioned and everything works fine, both in Python 2.4 and 2.5: [EMAIL PROTECTED]:~/Desktop/mysite$ python2.4 Python 2.4.4 (#2, Oct 4 2007, 22:02:31) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> [EMAIL PROTECTED]:~/Desktop/mysite$ python2.4 manage.py runserver Validating models... 0 errors found Django version 0.97-pre-SVN-6718, using settings 'mysite.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. 42 [09/Dec/2007 09:11:40] "GET / HTTP/1.1" 404 2053 [EMAIL PROTECTED]:~/Desktop/mysite$ python Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> [EMAIL PROTECTED]:~/Desktop/mysite$ python manage.py runserver Validating models... 0 errors found Django version 0.97-pre-SVN-6718, using settings 'mysite.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. 42 [09/Dec/2007 09:12:17] "GET / HTTP/1.1" 404 2053 Can you provide any other debugging information that might help me narrow down the problem? Adrian, what errors were you seeing that caused the revert? Todd (Sorry it took me so long to get to this--teaching has been a bear recently.) On Dec 4, 2007 5:37 PM, Josh Stone <[EMAIL PROTECTED]> wrote: > > I just found that commit 6871 fixed the problem by reverting 6718: > "Undid [6718], as it broke 'django-admin.py runserver' for a > reason I haven't figured out yet" > > But since there still seems to be some mystery, I went on with some > debugging on 6718 anyway below. > > On Dec 2, 6:53 am, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: > > Try to reduce the problem to something a bit simpler, since there's a > > large package involved here (that I, and probably a lot of other people > > on this list, know nothing about). > > I'm sorry, you're right, I should have pared down the problem first. > > > Does just creating a simple Django project from scratch work for you > > (e.g. the tutorial application)? > > I started a new 'mysite' as described in the beginning of the > tutorial, and verified that I could get the "Welcome to Django" page. > Then I made the following simple changes: > > Add to settings.py: > FOOBAR = 42 > > Add to urls.py: > from django.conf import settings > print settings.FOOBAR > > Then when I visit the site, I get an ImproperlyConfigured exception, > "Error while importing URLconf 'mysite.urls': 'Settings' object has no > attribute 'FOOBAR'". But if I add "--settings=mysite.settings" to the > manage.py command line, then it works fine. > > > What operating system are you running on (there could well be Windows > > vs. Mac vs. Linux vs. OS/2 differences)? What exceptions do you get? > > Just the standard "can't find settings" exception, or something else? > > This is RHEL5.1, with python-2.4.3-19.el5. The exception is always > the same, as quoted above. > > Let me know if I should try anything else. Otherwise I'll just use > Django after 6718 was reverted, where things are fine for me. > > Josh > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
