3 files changed, 23 insertions, 23 deletions

diff --git a/src/mailman/handlers/docs/owner-recips.rst b/src/mailman/handlers/docs/owner-recips.rst
index e62551ba6..ff9467b13 100644
--- a/src/mailman/handlers/docs/owner-recips.rst
+++ b/src/mailman/handlers/docs/owner-recips.rst
@@ -41,7 +41,7 @@ Anne disables her owner delivery, so she will not receive `-owner` emails.
     >>> handler.process(mlist_1, msg, msgdata)
     >>> dump_list(msgdata['recipients'])
     bart@example.com
-    
+
 If Bart also disables his owner delivery, then no one could contact the list's
 owners.  Since this is unacceptable, the site owner is used as a fallback.
 
@@ -55,7 +55,7 @@ For mailing lists which have no owners at all, the site owner is also used as
 a fallback.
 
     >>> mlist_2 = create_list('beta@example.com')
-    >>> mlist_2.administrators.member_count
+    >>> print(mlist_2.administrators.member_count)
     0
     >>> msgdata = {}
     >>> handler.process(mlist_2, msg, msgdata)
diff --git a/src/mailman/model/docs/autorespond.rst b/src/mailman/model/docs/autorespond.rst
index 6210e48cb..809de934a 100644
--- a/src/mailman/model/docs/autorespond.rst
+++ b/src/mailman/model/docs/autorespond.rst
@@ -37,34 +37,34 @@ have already been sent today.
     ...     'aperson@example.com')
 
     >>> from mailman.interfaces.autorespond import Response
-    >>> response_set.todays_count(address, Response.hold)
+    >>> print(response_set.todays_count(address, Response.hold))
     0
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     0
 
 Using the response set, we can record that a hold response is sent to the
 address.
 
     >>> response_set.response_sent(address, Response.hold)
-    >>> response_set.todays_count(address, Response.hold)
+    >>> print(response_set.todays_count(address, Response.hold))
     1
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     0
 
 We can also record that a command response was sent.
 
     >>> response_set.response_sent(address, Response.command)
-    >>> response_set.todays_count(address, Response.hold)
+    >>> print(response_set.todays_count(address, Response.hold))
     1
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     1
 
 Let's send one more.
 
     >>> response_set.response_sent(address, Response.command)
-    >>> response_set.todays_count(address, Response.hold)
+    >>> print(response_set.todays_count(address, Response.hold))
     1
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     2
 
 Now the day flips over and all the counts reset.
@@ -73,9 +73,9 @@ Now the day flips over and all the counts reset.
     >>> from mailman.utilities.datetime import factory
     >>> factory.fast_forward()
 
-    >>> response_set.todays_count(address, Response.hold)
+    >>> print(response_set.todays_count(address, Response.hold))
     0
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     0
 
 
@@ -110,7 +110,7 @@ If there's been no response sent to a particular address, None is returned.
 
     >>> address = getUtility(IUserManager).create_address(
     ...     'bperson@example.com')
-    >>> response_set.todays_count(address, Response.command)
+    >>> print(response_set.todays_count(address, Response.command))
     0
     >>> print(response_set.last_response(address, Response.command))
     None
diff --git a/src/mailman/model/docs/requests.rst b/src/mailman/model/docs/requests.rst
index e99cef634..1e1eba35a 100644
--- a/src/mailman/model/docs/requests.rst
+++ b/src/mailman/model/docs/requests.rst
@@ -35,7 +35,7 @@ Holding requests
 
 The list's requests database starts out empty.
 
-    >>> requests.count
+    >>> print(requests.count)
     0
     >>> dump_list(requests.held_requests)
     *Empty*
@@ -68,21 +68,21 @@ Getting requests
 
 We can see the total number of requests being held.
 
-    >>> requests.count
+    >>> print(requests.count)
     3
 
 We can also see the number of requests being held by request type.
 
-    >>> requests.count_of(RequestType.subscription)
+    >>> print(requests.count_of(RequestType.subscription))
     1
-    >>> requests.count_of(RequestType.unsubscription)
+    >>> print(requests.count_of(RequestType.unsubscription))
     1
 
 We can also see when there are multiple held requests of a particular type.
 
-    >>> requests.hold_request(RequestType.held_message, 'hold_4')
+    >>> print(requests.hold_request(RequestType.held_message, 'hold_4'))
     4
-    >>> requests.count_of(RequestType.held_message)
+    >>> print(requests.count_of(RequestType.held_message))
     2
 
 We can ask the requests database for a specific request, by providing the id
@@ -132,7 +132,7 @@ Iterating over requests
 To make it easier to find specific requests, the list requests can be iterated
 over by type.
 
-    >>> requests.count_of(RequestType.held_message)
+    >>> print(requests.count_of(RequestType.held_message))
     3
     >>> for request in requests.of_type(RequestType.held_message):
     ...     key, data = requests.get_request(request.id)
@@ -154,10 +154,10 @@ Deleting requests
 Once a specific request has been handled, it can be deleted from the requests
 database.
 
-    >>> requests.count
+    >>> print(requests.count)
     5
     >>> requests.delete_request(2)
-    >>> requests.count
+    >>> print(requests.count)
     4
 
 Request 2 is no longer in the database.
@@ -167,5 +167,5 @@ Request 2 is no longer in the database.
 
     >>> for request in requests.held_requests:
     ...     requests.delete_request(request.id)
-    >>> requests.count
+    >>> print(requests.count)
     0