-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 client Brotli support #5227
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5227 +/- ##
=======================================
Coverage 97.54% 97.54%
=======================================
Files 43 43
Lines 8794 8797 +3
Branches 1413 1413
=======================================
+ Hits 8578 8581 +3
Misses 101 101
Partials 115 115
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
The PR looks good.
Please click on https://cla-assistant.io/aio-libs/aiohttp?pullRequest=5227 to sign CLA.
I've added it recently and checked -- the sign is pretty easy :)
@asvetlov |
Oops. |
Signed. |
Sounds good. |
What about the dependencies section? Lines 146 to 170 in 021668a
|
ok |
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.
Ooops, the spell checker doesn't approve the docs changes: https://github.com/aio-libs/aiohttp/pull/5227/checks?check_run_id=1400046288
The most practical solution is extending https://github.com/aio-libs/aiohttp/blob/master/docs/spelling_wordlist.txt with words like brotli
to teach the checker new facilities
I fixed the spellcheck. |
The feature is backward compatible. |
The aiohttp user from #5219 wanted to use it. May be for 3.7.3? |
Sorry, I had no capacity to push it into 3.7.3. |
Thanks! |
💔 Backport was not successfulThe PR was attempted backported to the following branches:
|
hi 👋 it seems this patch didn't make it into 3.8.3, the Accept-Encoding header is still hard-coded. could this patch be cherry-picked into 3.8.4? |
Backport to 3.9: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 28ea32d on top of patchback/backports/3.9/28ea32d2282728a94af73c87efd6ab314c14320e/pr-5227 Backporting merged PR #5227 into master
🤖 @patchback |
You can try following bot instructions to submit a PR against 3.9. |
(cherry picked from commit 28ea32d)
(cherry picked from commit 28ea32d) backport ref #5227 (comment) Co-authored-by: Dmitry Erlikh <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
hi 👋 is there a rough ETA when 3.9 and/or 4.0 will be shipped? |
What do these changes do?
If brotlipy is installed, client will support this compression type
Are there changes in behavior for the user?
No
Related issue number
#5219
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.