From ec020cab7ef4b1943a8fe9a4d6872f7e874db707 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 30 Dec 2013 17:59:18 -0500 Subject: [PATCH] Fixed a broken link in docs/intro/tutorial01.txt. --- docs/intro/tutorial01.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt index 0bd3d0abaf..3fa07e132c 100644 --- a/docs/intro/tutorial01.txt +++ b/docs/intro/tutorial01.txt @@ -696,7 +696,7 @@ automatically-generated admin. :meth:`~django.db.models.Model.__unicode__` and converts the result to a UTF-8 bytestring. This means that ``unicode(p)`` will return a Unicode string, and ``str(p)`` will return a bytestring, with characters encoded - as UTF-8. Python does the opposite: :class:`object` has a ``__unicode__`` + as UTF-8. Python does the opposite: ``object`` has a ``__unicode__`` method that calls ``__str__`` and interprets the result as an ASCII bytestring. This difference can create confusion.