From de99f558d806a2a1b30072ec95bc44d412d80dab Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 25 Sep 2015 13:28:12 -0400 Subject: Fixed #25462 -- Removed Model.__unicode__() in favor of @python_2_unicode_compatible. --- docs/topics/db/models.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/topics') diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index ed13e46374..53d2396f03 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -756,9 +756,6 @@ You can override most of these -- see `overriding predefined model methods`_, below -- but there are a couple that you'll almost always want to define: :meth:`~Model.__str__` (Python 3) - Python 3 equivalent of ``__unicode__()``. - -:meth:`~Model.__unicode__` (Python 2) A Python "magic method" that returns a unicode "representation" of any object. This is what Python and Django will use whenever a model instance needs to be coerced and displayed as a plain string. Most @@ -768,6 +765,9 @@ below -- but there are a couple that you'll almost always want to define: You'll always want to define this method; the default isn't very helpful at all. +``__unicode__()`` (Python 2) + Python 2 equivalent of ``__str__()``. + :meth:`~Model.get_absolute_url` This tells Django how to calculate the URL for an object. Django uses this in its admin interface, and any time it needs to figure out a URL -- cgit v1.3