New submission from Vitaly Kruglikov <>:

`asyncio.WriteTransport.set_write_buffer_limits()` uses an unintuitive order of 
the args (high, low). I would expect `low` to be the first arg, especially 
since `asyncio.WriteTransport.get_write_buffer_limits()` returns them in the 
opposite order. This ordering and inconsistency with the companion function's 
return value is error-prone. See

components: asyncio
messages: 313423
nosy: asvetlov, vitaly.krug, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.WriteTransport.set_write_buffer_limits orders its args 
unintuitively and inconsistently with its companion function's return value
type: behavior
versions: Python 3.6, Python 3.7

Python tracker <>
Python-bugs-list mailing list

Reply via email to