From 227cec686e512412f613c3d14743b85445765d92 Mon Sep 17 00:00:00 2001 From: Alex Ogier Date: Thu, 3 May 2012 08:57:22 +0200 Subject: Fixed #18214 -- Clarified the docs about serializable objects. --- docs/topics/serialization.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt index d5a5282945..6bda32dece 100644 --- a/docs/topics/serialization.txt +++ b/docs/topics/serialization.txt @@ -3,8 +3,8 @@ Serializing Django objects ========================== Django's serialization framework provides a mechanism for "translating" Django -objects into other formats. Usually these other formats will be text-based and -used for sending Django objects over a wire, but it's possible for a +models into other formats. Usually these other formats will be text-based and +used for sending Django data over a wire, but it's possible for a serializer to handle any format (text-based or not). .. seealso:: @@ -23,8 +23,8 @@ At the highest level, serializing data is a very simple operation:: The arguments to the ``serialize`` function are the format to serialize the data to (see `Serialization formats`_) and a :class:`~django.db.models.query.QuerySet` to serialize. (Actually, the second -argument can be any iterator that yields Django objects, but it'll almost -always be a QuerySet). +argument can be any iterator that yields Django model instances, but it'll +almost always be a QuerySet). You can also use a serializer object directly:: -- cgit v1.3