summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2008-08-30 05:09:03 +0000
committerMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2008-08-30 05:09:03 +0000
commitc0b53b3dcc817aa6522b4477f009e7c3bb83ae2e (patch)
treebccb5e82f148b1078653e66ab950c13c24b2c831 /docs
parentfd0cc45828e11e5e8936817e7a76c6bd5a8d0460 (diff)
Removed the need for ROOT_URLCONF in settings when running Django's core tests
(via runtests.py). It was embarrassing having to explain the need for it to people, since we ignore whatever setting is passed in. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8731 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/contributing.txt3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/internals/contributing.txt b/docs/internals/contributing.txt
index 2c08bcd77b..9cce80e3c9 100644
--- a/docs/internals/contributing.txt
+++ b/docs/internals/contributing.txt
@@ -730,8 +730,7 @@ To run the tests, ``cd`` to the ``tests/`` directory and type:
./runtests.py --settings=path.to.django.settings
Yes, the unit tests need a settings module, but only for database connection
-info, with the ``DATABASE_ENGINE`` setting. You'll also need a ``ROOT_URLCONF``
-setting (its value is ignored; it just needs to be present).
+info, with the ``DATABASE_ENGINE`` setting.
If you're using the ``sqlite3`` database backend, no further settings are
needed. A temporary database will be created in memory when running the tests.