-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add additional clarification for creating objects that require a running event loop #8583
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8583 +/- ##
==========================================
- Coverage 97.70% 97.64% -0.07%
==========================================
Files 107 107
Lines 33443 33443
Branches 3927 3927
==========================================
- Hits 32677 32655 -22
- Misses 555 573 +18
- Partials 211 215 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #8585 🤖 @patchback |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #8586 🤖 @patchback |
…reating objects that require a running event loop (#8585) Co-authored-by: J. Nick Koston <nick@koston.org>
…reating objects that require a running event loop (#8586) Co-authored-by: J. Nick Koston <nick@koston.org>
aiohttp 3.10.0 removed the ability to create `aiohttp.ClientSession` instances without a running event loop (see aio-libs/aiohttp#8583), but a few of blinkpy's tests relied on that.
aiohttp 3.10.0 removed the ability to create `aiohttp.ClientSession` instances without a running event loop (see aio-libs/aiohttp#8583), but one of yalexs's tests relied on that.
aiohttp 3.10.0 removed the ability to create `aiohttp.ClientSession` instances without a running event loop (see aio-libs/aiohttp#8583), but one of yalexs's tests relied on that.
What do these changes do?
Adjust changelog message to further clarify #6378.
References #8555