[New-bugs-announce] [issue38164] poloshing asyncio Streams API
Yury Selivanov
report at bugs.python.org
Fri Sep 13 13:11:32 EDT 2019
New submission from Yury Selivanov <yselivanov at gmail.com>:
Summary of discussion at https://github.com/python-trio/trio/issues/1208:
* `asyncio.Stream.write()` will start throwing a `DeprecationWarning` asking people to add an `await` if they didn't;
* `asyncio.Stream.close()` will start throwing a `DeprecationWarning` asking people to add an `await` if they didn't;
* `asyncio.Stream.drain()` & `asyncio.Stream.wait_closed()` will start throwing a `DeprecationWarning` telling about a scheduled removal (in Python 3.12) when used on `Process.std*` streams;
* `asyncio.Stream.drain()` & `asyncio.Stream.wait_closed()` will not work at all on Streams created via new 3.8 APIs: `connect()` & `StreamServer`.
----------
assignee: asvetlov
components: asyncio
messages: 352372
nosy: asvetlov, lukasz.langa, yselivanov
priority: release blocker
severity: normal
stage: needs patch
status: open
title: poloshing asyncio Streams API
type: behavior
versions: Python 3.8
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38164>
_______________________________________
More information about the New-bugs-announce
mailing list