mirror of
https://github.com/django/django.git
synced 2024-12-26 02:56:25 +00:00
d4a0b27838
* Renamed the __unicode__ methods * Applied the python_2_unicode_compatible decorator * Removed the StrAndUnicode mix-in that is superseded by python_2_unicode_compatible * Kept the __unicode__ methods in classes that specifically test it under Python 2
37 lines
1.3 KiB
Python
37 lines
1.3 KiB
Python
# -*- coding: utf-8 -*-
|
|
"""
|
|
2. Adding __str__() or __unicode__() to models
|
|
|
|
Although it's not a strict requirement, each model should have a
|
|
``_str__()`` or ``__unicode__()`` method to return a "human-readable"
|
|
representation of the object. Do this not only for your own sanity when dealing
|
|
with the interactive prompt, but also because objects' representations are used
|
|
throughout Django's automatically-generated admin.
|
|
|
|
Normally, you should write ``__unicode__()`` method, since this will work for
|
|
all field types (and Django will automatically provide an appropriate
|
|
``__str__()`` method). However, you can write a ``__str__()`` method directly,
|
|
if you prefer. You must be careful to encode the results correctly, though.
|
|
"""
|
|
|
|
from django.db import models
|
|
from django.utils.encoding import python_2_unicode_compatible
|
|
|
|
|
|
class Article(models.Model):
|
|
headline = models.CharField(max_length=100)
|
|
pub_date = models.DateTimeField()
|
|
|
|
def __str__(self):
|
|
# Caution: this is only safe if you are certain that headline will be
|
|
# in ASCII.
|
|
return self.headline
|
|
|
|
@python_2_unicode_compatible
|
|
class InternationalArticle(models.Model):
|
|
headline = models.CharField(max_length=100)
|
|
pub_date = models.DateTimeField()
|
|
|
|
def __str__(self):
|
|
return self.headline
|