-
Notifications
You must be signed in to change notification settings - Fork 86
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
fix: aiohttp 3.9 _writer can't await #248
fix: aiohttp 3.9 _writer can't await #248
Conversation
Co-authored-by: Sam Bull <[email protected]>
Hi, Can any maintainer check this? This weekend if all goes according to plan aiohttp 3.9 will be released, and at that time this change will be necessary. |
When could a new version with this correction be released? aiohttp 3.9 has already been released and I need this fix to be published in a release so I can update my systems. |
Can the new version of this be released? |
@pnuckowski If possible, please release it, I am an upcoming committer from Flyte, we need it. |
Ya esta publicada, la versión 0.7.6 |
Now that docker-base has aiohttp 3.9.3, get the latest aioresponses. This fixes a bug that "object Mock can't be used in 'await' expression" (see pnuckowski/aioresponses#248), which affects the 7 unit tests in test_fetch_aiohttp using the `mock_aioresponses` fixture.
Now that docker-base has aiohttp 3.9.3, get the latest aioresponses. This fixes a bug that "object Mock can't be used in 'await' expression" (see pnuckowski/aioresponses#248), which affects the 7 unit tests in test_fetch_aiohttp using the `mock_aioresponses` fixture. It seems that aioresponses 0.7.6 needs Python 3.7 while katsdpmodels itself still only requires Python 3.6. This discrepancy seems OK for now as the tests are run on Python 3.8 and soon the minimum version will be bumped anyway.
Fixed the problem mentioned in bug #247 and aio-libs/aiohttp#7675 (comment)