Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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? Sign in to your account

Jump to bottom

Wrong exception object passed to error callback if someone calls transport.close() method #152

Open
Bahus opened this issue Aug 7, 2017 · 0 comments
Open

Wrong exception object passed to error callback if someone calls transport.close() method #152

Bahus opened this issue Aug 7, 2017 · 0 comments

Comments

@Bahus
Copy link

Bahus commented Aug 7, 2017

Please check my comments to the commit: e8304b8#commitcomment-23516974:

I can't decide what exactly happened in my custom error callback, since I get object ChannelClosed(None, None), 'Channel is closed' instead of None: https://docs.python.org/3/library/asyncio-protocol.html#asyncio.BaseTransport.close
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Bahus