This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author socketpair
Recipients docs@python, socketpair
Date 2015-11-27.23:22:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448666524.97.0.228973534452.issue25756@psf.upfronthosting.co.za>
In-reply-to
Content
Here is the match against master.


Doc/library/asyncio-protocol.rst:

@@ -156,9 +156,9 @@ WriteTransport
       high-water limit is given, the low-water limit defaults to an
       implementation-specific value less than or equal to the
       high-water limit.  Setting *high* to zero forces *low* to zero as
-      well, and causes :meth:`pause_writing` to be called whenever the
+      well, and causes :meth:`resume_writing` to be called whenever the
       buffer becomes non-empty.  Setting *low* to zero causes
-      :meth:`resume_writing` to be called only once the buffer is empty.
+      :meth:`pause_writing` to be called only once the buffer is empty.
       Use of zero for either limit is generally sub-optimal as it
       reduces opportunities for doing I/O and computation
       concurrently.
History
Date User Action Args
2015-11-27 23:22:05socketpairsetrecipients: + socketpair, docs@python
2015-11-27 23:22:04socketpairsetmessageid: <1448666524.97.0.228973534452.issue25756@psf.upfronthosting.co.za>
2015-11-27 23:22:04socketpairlinkissue25756 messages
2015-11-27 23:22:04socketpaircreate