[1.6.x] Fixed #20691 -- Added a note for __str__() vs. __unicode__() and Python 3.
Thanks garrison for the suggestion.
Backport of 8a679386c3
from master.
This commit is contained in:
parent
5ecdf0eb9c
commit
b36f55c5a5
|
@ -240,6 +240,13 @@ Django will convert it to Unicode when it needs to.
|
|||
Choosing between ``__str__()`` and ``__unicode__()``
|
||||
----------------------------------------------------
|
||||
|
||||
.. note::
|
||||
|
||||
If you are on Python 3, you can skip this section because you'll always
|
||||
create ``__str__()`` rather than ``__unicode__()``. If you'd like
|
||||
compatibility with Python 2, you can decorate your model class with
|
||||
:func:`~django.utils.encoding.python_2_unicode_compatible`.
|
||||
|
||||
One consequence of using Unicode by default is that you have to take some care
|
||||
when printing data from the model.
|
||||
|
||||
|
|
Loading…
Reference in New Issue