[New-bugs-announce] [issue25756] asyncio WriteTransport documentation typo
report at bugs.python.org
Fri Nov 27 18:22:04 EST 2015
New submission from Марк Коренберг:
Here is the match against master.
@@ -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
assignee: docs at python
nosy: docs at python, mmarkk
title: asyncio WriteTransport documentation typo
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce