-
Notifications
You must be signed in to change notification settings - Fork 151
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.
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
Test for, and suppress, additional get_event_loop() DeprecationWarnings #817
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #817 +/- ##
=======================================
Coverage 95.59% 95.59%
=======================================
Files 2 2
Lines 477 477
Branches 96 95 -1
=======================================
Hits 456 456
Misses 12 12
Partials 9 9 ☔ View full report in Codecov by Sentry. |
I don't think this matters, but maybe...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for looking into this!
We can only reproduce this on specific Python 3.10.x patch versions, but we can't easily test those in CI. Give up the attempt.
@seifertm Ping—do the latest changes address your feedback? |
Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They do. Thank you for the patch.
I'll aim for a release this week.
This attempts to do what's described in #757 (comment), to solve continued instances of issue #757:
Add tests to catch any lingeringasyncio.get_event_loop()
DeprecationWarning
s.The existing tests are already catching a bunch, but only when they're run under specific Python patch versions. So the test part of this PR just configures tox and GitHub Actions to do that.