Ticket #13662: 13662.diff

README

@@ -40 +40 @@
 
 To run Django's included unit tests:
 
-    * Follow the instructions in the section "Unit tests" in
-      docs/faq/contributing.txt, published online at http://docs.djangoproject.com/en/dev/internals/contributing/#claiming-tickets#unit-tests
- No newline at end of file
+    * Follow the instructions in the "Unit tests" section of
+      docs/internals/contributing.txt, published online at http://docs.djangoproject.com/en/dev/internals/contributing/#running-the-unit-tests

docs/internals/contributing.txt

@@ -877 +877 @@
 Quickstart
 ~~~~~~~~~~
 
-Running the tests requires a Django settings module that defines the databases to
-use. To run the tests with the included minimal ``settings`` module, ``cd`` to the
-Django ``tests/`` directory and type:
+Running the tests requires a Django settings module that defines the databases
+to use. To run the tests with the included minimal ``settings`` module, ``cd``
+to the Django ``tests/`` directory and type:
 
 .. code-block:: bash
 
     ./runtests.py --settings=test_sqlite
 
-Using the included ``test_sqlite.py`` allows you to get started running the tests
-against the SQLite database backend without doing anything else on your
+Using the included ``test_sqlite.py`` allows you to get started running the
+tests against the SQLite database backend without doing anything else on your
 filesystem. However it should be noted that running against other database
 backends is recommended for certain types of test cases.
 
-If you get an ``ImportError: No module named django.contrib`` error, you need to add your distribution of Django to your ``PYTHONPATH`` - see `Pointing Python at the new Django version`_ below.
+If you get an ``ImportError: No module named django.contrib`` error, you need
+to add your distribution of Django to your ``PYTHONPATH``. This can be done
+temporarily by symlinking the django directory. To do so, type:
+
+.. code-block:: bash
+
+    ln -s ../django/ django
+
+For more details, and better options if you plan on using this version of
+Django long-term, read `Pointing Python at the new Django version`_ below.
 
 Using another ``settings`` module
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~