      the parent class and then don't use them later on. It's up to you whether
      you want your fields to be more strict about the options they select, or
      to use the simpler, more permissive behavior of the current fields.
  
  The :meth:`~django.db.models.Field.__init__` method takes the following
  parameters:
  
      * :attr:`~django.db.models.Field.verbose_name`
      * :attr:`~django.db.models.Field.name`
      * :attr:`~django.db.models.Field.primary_key`
 
</s> remove :meth:`to_python`::
 </s> add :meth:`.to_python`:: </s> remove :meth:`get_db_prep_value` is the method where those conversions should
 </s> add :meth:`.get_db_prep_value` is the method where those conversions should </s> remove If you use :class:`~django.db.models.SubfieldBase`, :meth:`to_python`
 </s> add If you use :class:`~django.db.models.SubfieldBase`, :meth:`.to_python` </s> remove and pass the rest to the :meth:`get_db_prep_lookup` method of the parent class.
 </s> add and pass the rest to the :meth:`.get_db_prep_lookup` method of the parent class. </s> remove The :meth:`db_type` method is only called by Django when the framework
constructs the ``CREATE TABLE`` statements for your application -- that is, when
you first create your tables. It's not called at any other time, so it can
afford to execute slightly complex code, such as the ``connection.settings_dict``
check in the above example.
 </s> add The :meth:`.db_type` method is only called by Django when the framework
constructs the ``CREATE TABLE`` statements for your application -- that is,
when you first create your tables. It's not called at any other time, so it can
afford to execute slightly complex code, such as the
``connection.settings_dict`` check in the above example.
.. method:: Field.__init__

      the parent class and then don't use them later on. It's up to you whether
      you want your fields to be more strict about the options they select, or
      to use the simpler, more permissive behavior of the current fields.
  
.. method:: Field.__init__

  The :meth:`~django.db.models.Field.__init__` method takes the following
  parameters:
  
      * :attr:`~django.db.models.Field.verbose_name`
      * :attr:`~django.db.models.Field.name`
      * :attr:`~django.db.models.Field.primary_key`
keep keep keep add keep keep keep keep keep keep
 Fixed #15308 -- Sphinx/reST fixes for the Custom Model Fields docs.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15547 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/howto/custom-model-fields.txt