-
Notifications
You must be signed in to change notification settings - Fork 95
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
auto_decompress not supported as keyword argument for aiohttp<3.9 #716
Comments
Hi @sebastianmika, thanks for bringing this up. Previous to the addition of the |
I am seeing your point and the advantage. My challenge (and I am likely not alone) is that I have plenty of Looking at the recent PR I was wondering whether a very similar result couldn't have been achieved by making the user pass in a |
Yes, that would be a valid option too. I was trying to achieve it on call-by-call basis as we usually have a single storage object for the whole application, and you could have different use cases within it. Still, I see that we do accept a session parameter on both |
Ah, good catch on this. I would rather avoid upgrading the I plan to do the following:
|
That would have worked for aio (barring the call-by-call changes you called out), but unfortunately not for rest, since our internal usage of the |
With the latest release of
gcloud-aio-auth/storage
(5.3.0) the following breaks when usingaiohttp<3.9
, which is allowed since the minimal required version is currentlyaiohttp>=3.3.0
.Potential fixes:
aiohttp>=3.9
allow_redirects=allow_redirects
when setting up theself.ClientSession
object in line 556 ofgcloud/aio/storage/storage.py
and remove from the.get
calls (and probably other places)Code to reproduce with
aiohttp==3.8.6
:The text was updated successfully, but these errors were encountered: