New submission from Марк Коренберг:
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.
----------
assignee: docs@python
components: Documentation
messages: 255508
nosy: docs@python, mmarkk
priority: normal
severity: normal
status: open
title: asyncio WriteTransport documentation typo
type: enhancement
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25756>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
