Replaced print statement by print function (forward compatibility syntax).

3 files changed, 16 insertions, 16 deletions

diff --git a/docs/topics/db/examples/many_to_many.txt b/docs/topics/db/examples/many_to_many.txt
index 1ad89e71bf..5a24027894 100644
--- a/docs/topics/db/examples/many_to_many.txt
+++ b/docs/topics/db/examples/many_to_many.txt
@@ -263,14 +263,14 @@ Bulk delete some Publications - references to deleted publications should go::
 Bulk delete some articles - references to deleted objects should go::
 
     >>> q = Article.objects.filter(headline__startswith='Django')
-    >>> print q
+    >>> print(q)
     [<Article: Django lets you build Web apps easily>]
     >>> q.delete()
 
 After the delete, the QuerySet cache needs to be cleared, and the referenced
 objects should be gone::
 
-    >>> print q
+    >>> print(q)
     []
     >>> p1.article_set.all()
     [<Article: NASA uses Python>]
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index 0a67b9b486..7782f1c3ed 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -284,10 +284,10 @@ actually run the query until the :class:`~django.db.models.query.QuerySet` is
     >>> q = Entry.objects.filter(headline__startswith="What")
     >>> q = q.filter(pub_date__lte=datetime.now())
     >>> q = q.exclude(body_text__icontains="food")
-    >>> print q
+    >>> print(q)
 
 Though this looks like three database hits, in fact it hits the database only
-once, at the last line (``print q``). In general, the results of a
+once, at the last line (``print(q)``). In general, the results of a
 :class:`~django.db.models.query.QuerySet` aren't fetched from the database
 until you "ask" for them. When you do, the
 :class:`~django.db.models.query.QuerySet` is *evaluated* by accessing the
@@ -720,8 +720,8 @@ your :class:`~django.db.models.query.QuerySet`\s correctly. For example, the
 following will create two :class:`~django.db.models.query.QuerySet`\s, evaluate
 them, and throw them away::
 
-    >>> print [e.headline for e in Entry.objects.all()]
-    >>> print [e.pub_date for e in Entry.objects.all()]
+    >>> print([e.headline for e in Entry.objects.all()])
+    >>> print([e.pub_date for e in Entry.objects.all()])
 
 That means the same database query will be executed twice, effectively doubling
 your database load. Also, there's a possibility the two lists may not include
@@ -732,8 +732,8 @@ To avoid this problem, simply save the
 :class:`~django.db.models.query.QuerySet` and reuse it::
 
     >>> queryset = Entry.objects.all()
-    >>> print [p.headline for p in queryset] # Evaluate the query set.
-    >>> print [p.pub_date for p in queryset] # Re-use the cache from the evaluation.
+    >>> print([p.headline for p in queryset]) # Evaluate the query set.
+    >>> print([p.pub_date for p in queryset]) # Re-use the cache from the evaluation.
 
 .. _complex-lookups-with-q:
 
@@ -1055,16 +1055,16 @@ related object is accessed. Subsequent accesses to the foreign key on the same
 object instance are cached. Example::
 
     >>> e = Entry.objects.get(id=2)
-    >>> print e.blog  # Hits the database to retrieve the associated Blog.
-    >>> print e.blog  # Doesn't hit the database; uses cached version.
+    >>> print(e.blog)  # Hits the database to retrieve the associated Blog.
+    >>> print(e.blog)  # Doesn't hit the database; uses cached version.
 
 Note that the :meth:`~django.db.models.query.QuerySet.select_related`
 :class:`~django.db.models.query.QuerySet` method recursively prepopulates the
 cache of all one-to-many relationships ahead of time. Example::
 
     >>> e = Entry.objects.select_related().get(id=2)
-    >>> print e.blog  # Doesn't hit the database; uses cached version.
-    >>> print e.blog  # Doesn't hit the database; uses cached version.
+    >>> print(e.blog)  # Doesn't hit the database; uses cached version.
+    >>> print(e.blog)  # Doesn't hit the database; uses cached version.
 
 .. _backwards-related-objects:
 
diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt
index 658dfdf859..2ac47170aa 100644
--- a/docs/topics/db/sql.txt
+++ b/docs/topics/db/sql.txt
@@ -40,7 +40,7 @@ This is best illustrated with an example. Suppose you've got the following model
 You could then execute custom SQL like so::
 
     >>> for p in Person.objects.raw('SELECT * FROM myapp_person'):
-    ...     print p
+    ...     print(p)
     John Smith
     Jane Jones
 
@@ -128,8 +128,8 @@ The ``Person`` objects returned by this query will be deferred model instances
 fields that are omitted from the query will be loaded on demand. For example::
 
     >>> for p in Person.objects.raw('SELECT id, first_name FROM myapp_person'):
-    ...     print p.first_name, # This will be retrieved by the original query
-    ...     print p.last_name # This will be retrieved on demand
+    ...     print(p.first_name, # This will be retrieved by the original query
+    ...           p.last_name) # This will be retrieved on demand
     ...
     John Smith
     Jane Jones
@@ -153,7 +153,7 @@ of people with their ages calculated by the database::
 
     >>> people = Person.objects.raw('SELECT *, age(birth_date) AS age FROM myapp_person')
     >>> for p in people:
-    ...     print "%s is %s." % (p.first_name, p.age)
+    ...     print("%s is %s." % (p.first_name, p.age))
     John is 37.
     Jane is 42.
     ...