Skip to content

Commit

Permalink
[1.0.X] Fixed #9734 -- Typo fix in the custom fields documentation, p…
Browse files Browse the repository at this point in the history
…ointed out by

col16.

Backport of r9557 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9560 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information
malcolmt committed Dec 3, 2008
1 parent 500021a commit 8c6a6f3
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/howto/custom-model-fields.txt
Expand Up @@ -31,12 +31,12 @@ Our example object
------------------

Creating custom fields requires a bit of attention to detail. To make things
easier to follow, we'll use a consistent example throughout this document.
Suppose you have a Python object representing the deal of cards in a hand of
Bridge_. (Don't worry, you don't know how to play Bridge to follow this
example. You only need to know that 52 cards are dealt out equally to four
players, who are traditionally called *north*, *east*, *south* and *west*.)
Our class looks something like this::
easier to follow, we'll use a consistent example throughout this document:
wrapping a Python object representing the deal of cards in a hand of Bridge_.
Don't worry, you don't have know how to play Bridge to follow this example.
You only need to know that 52 cards are dealt out equally to four players, who
are traditionally called *north*, *east*, *south* and *west*. Our class looks
something like this::

class Hand(object):
def __init__(self, north, east, south, west):
Expand Down

0 comments on commit 8c6a6f3

Please sign in to comment.