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/internals/contributing/writing-code/coding-style.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/internals/contributing/writing-code/coding-style.txt') diff --git a/docs/internals/contributing/writing-code/coding-style.txt b/docs/internals/contributing/writing-code/coding-style.txt index 21146600b4..437d2f7ec5 100644 --- a/docs/internals/contributing/writing-code/coding-style.txt +++ b/docs/internals/contributing/writing-code/coding-style.txt @@ -124,13 +124,16 @@ Model style first_name = models.CharField(max_length=20) last_name = models.CharField(max_length=40) +* If you define a ``__str__`` method (previously ``__unicode__`` before Python 3 + was supported), decorate the model class with + :func:`~django.utils.encoding.python_2_unicode_compatible`. + * The order of model inner classes and standard methods should be as follows (noting that these are not all required): * All database fields * Custom manager attributes * ``class Meta`` - * ``def __unicode__()`` * ``def __str__()`` * ``def save()`` * ``def get_absolute_url()`` -- cgit v1.3