Small cleanups to the websocket frame sender#8933
Conversation
- Add some comments about what is going on in _send_frame since much of the logic is not obvious - Avoid fetch the len() in a few places where its a fixed value and already known
- Add some comments about what is going on in _send_frame since much of the logic is not obvious - Avoid fetch the len() in a few places where its a fixed value and already known
- Add some comments about what is going on in _send_frame since much of the logic is not obvious - Avoid fetch the len() in a few places where its a fixed value and already known
- Add some comments about what is going on in _send_frame since much of the logic is not obvious - Avoid fetch the len() in a few places where its a fixed value and already known
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #8933 +/- ##
=======================================
Coverage 98.25% 98.25%
=======================================
Files 107 107
Lines 34136 34139 +3
Branches 4048 4047 -1
=======================================
+ Hits 33541 33544 +3
Misses 421 421
Partials 174 174
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 #8978 🤖 @patchback |
(cherry picked from commit 8f3b1f4)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #8979 🤖 @patchback |
(cherry picked from commit 8f3b1f4)
…ame sender (#8978) Co-authored-by: J. Nick Koston <nick@koston.org>
…ame sender (#8979) Co-authored-by: J. Nick Koston <nick@koston.org>
What do these changes do?
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no