From 7442eb1a242ecf9d186d4e7de1b94e360e04782d Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Thu, 4 Jul 2013 15:19:33 +0200 Subject: Fixed #20224 -- Update docs examples which mention __unicode__ Thanks Marc Tamlyn and Tim Graham for the review. --- docs/howto/custom-model-fields.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/howto') diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 85c71004f4..5a5bef9141 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -710,9 +710,9 @@ smoothly: behavior of the field code is to call :func:`~django.utils.encoding.force_text` on the value. (In our examples in this document, ``value`` would be a ``Hand`` instance, not a - ``HandField``). So if your ``__unicode__()`` method automatically - converts to the string form of your Python object, you can save yourself - a lot of work. + ``HandField``). So if your ``__unicode__()`` method (``__str__()`` on + Python 3) automatically converts to the string form of your Python object, + you can save yourself a lot of work. Writing a ``FileField`` subclass -- cgit v1.3