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

Use public .is_closed() instead of private ._check_closed() from asyncio #98

Open
shamrin opened this issue Jan 5, 2021 · 0 comments
Open

Use public .is_closed() instead of private ._check_closed() from asyncio #98

shamrin opened this issue Jan 5, 2021 · 0 comments
Labels
good first issue

Comments

@shamrin
Copy link
Contributor

shamrin commented Jan 5, 2021

trio-asyncio use private asyncio.BaseEventLoop._check_closed() method everywhere.

We may want to switch to public .is_closed() instead. It was introduced in Python 3.5.

See also: #96 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shamrin