diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt
index 75d14e6..9f9fab1 100644
a
|
b
|
If you want your code to work on Python 2 & 3, you can use
|
362 | 362 | class HandField(with_metaclass(models.SubfieldBase, models.Field)): |
363 | 363 | ... |
364 | 364 | |
365 | | This ensures that the :meth:`.to_python` method, documented below, will always |
| 365 | This ensures that the :meth:`.to_python` method, will always |
366 | 366 | be called when the attribute is initialized. |
367 | 367 | |
368 | 368 | ModelForms and custom fields |
369 | 369 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
370 | 370 | |
371 | 371 | If you use :class:`~django.db.models.SubfieldBase`, :meth:`.to_python` |
372 | | will be called every time an instance of the field is assigned a |
| 372 | apart from its usual call when getting the value from the database, |
| 373 | will also be called every time an instance of the field is assigned a |
373 | 374 | value. This means that whenever a value may be assigned to the field, |
374 | 375 | you need to ensure that it will be of the correct datatype, or that |
375 | 376 | you handle any exceptions. |
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 9c58505..bcc5ead 100644
a
|
b
|
Field API reference
|
1615 | 1615 | The default implementation returns ``value``, which is the common case |
1616 | 1616 | when the database backend already returns the correct Python type. |
1617 | 1617 | |
1618 | | See :ref:`converting-database-values-to-python-objects` for usage. |
| 1618 | See :ref:`converting-database-values-to-python-objects` for various usages. |
1619 | 1619 | |
1620 | 1620 | When saving, :meth:`pre_save` and :meth:`get_db_prep_save` are used: |
1621 | 1621 | |