Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
assignee = None
closed_at = <Date 2018-01-24.23:21:26.170>
created_at = <Date 2017-12-20.19:12:25.492>
labels = ['3.7', 'type-feature', 'library', 'expert-asyncio']
title = 'Add StreamWriter.wait_closed()'
updated_at = <Date 2018-01-24.23:21:26.169>
user = 'https://github.com/asvetlov'
activity = <Date 2018-01-24.23:21:26.169>
actor = 'asvetlov'
assignee = 'none'
closed = True
closed_date = <Date 2018-01-24.23:21:26.170>
closer = 'asvetlov'
components = ['Library (Lib)', 'asyncio']
creation = <Date 2017-12-20.19:12:25.492>
creator = 'asvetlov'
dependencies = 
files = 
hgrepos = 
issue_num = 32391
keywords = ['patch']
message_count = 3.0
messages = ['308780', '308781', '310640']
nosy_count = 4.0
nosy_names = ['njs', 'asvetlov', 'yselivanov', 'nitishch']
pr_nums = ['5281']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32391'
versions = ['Python 3.7']
The text was updated successfully, but these errors were encountered:
Without the method there is no possibility to wait for actual writer closing (it's performed at least on next loop iteration, and even later for SSL transports).
Without waiting for actual closing writing tests is a pain: user should either add asyncio.sleep() after writer closing or suppress many warnings about unclosed resources.
Sorry, something went wrong.
We've discussed this before, please go ahead.
New changeset fe133aa by Andrew Svetlov in branch 'master':
bpo-32391: Implement StreamWriter.wait_closed() (bpo-5281)
No branches or pull requests