> Overall I get the impression we're muddled on the answer to: > > Should the auth tests pass out-of-the-box, independent of other project > configuration? > > Someone making a firm decision on that would help. Personally I'd favor > "yes" as the answer, but I don't feel very strongly about the issue. I'd > accept "no", but if the answer turns out to be "no" I think we should be > consistent on it, and document the requirements for getting "manage.py test" > to pass cleanly in a new project. (And by that I mean list what the > necessary templates are and what characteristics they need -- saying include > 'django.contrib.admin' in INSTALLED_APPS isn't what I mean by documenting > this.)
Karen summarizes my frustration fairly well -- While I'd like a clean test-pass on a new project, I don't _mind_ creating the templates as needed as part of the getting-started process. It just feels a bit back-door. However, if it's important enough to cause tests to fail, it should be equally visible & well-documented in various "starting a new project" docs as well as the testing section with special notes about (not) including contrib.admin in INSTALLED_APPS. -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
