Updating an older codebase to SVN HEAD, I got a slew of testing errors that I couldn't trace to my code. So I created a new empty project, tossed in some sqlite DB settings, and did a "manage.py test" which failed. It seems to be related to this ticket[1].
Steps to reproduce: bash$ django-admin.py startproject bug bash$ cd bug [add some DB settings] bash$ sed -i -e "/DATABASE_ENGINE/s/''/'sqlite3'/" -e "/DATABASE_NAME/s/''/'bug.db'/" settings.py bash$ ./manage.py test [loads of test failures here] I can hack it by adding django.contrib.admin to my list of INSTALLED_APPS, or by creating all these missing templates myself, but it seems broken to have tests fail out of the box when Django has perfectly good templates available. I didn't notice anything in the testing docs[2] that warns about this, and the tutorial adds django.contrib.admin but elides the detail that omitting the admin (described as optional[3]) causes test failure. Ticket #7611 is closed/wontfix :-( -tim [1] http://code.djangoproject.com/ticket/7611 [2] http://docs.djangoproject.com/en/dev/topics/testing/ [3] http://www.djangobook.com/en/2.0/chapter06/#s-the-django-contrib-packages "You can think of django.contrib as Django equivalent of the Python standard library -- optional, de facto implementations of common patterns." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
