-
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 compat with aiohttp 3.11.0+ #262
Conversation
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.
This looks sensible to me, although I admittedly don't know the internals of the library. Approving in spirit but I'm not sure this should be enough to merge it.
Because of aio-libs/aiohttp#9866 some tests are failing. This PR can be reverted when pnuckowski/aioresponses#262 is merged and released
Because of aio-libs/aiohttp#9866 some tests are failing. This PR can be reverted when pnuckowski/aioresponses#262 is merged and released
Because of aio-libs/aiohttp#9866 some tests are failing. This PR can be reverted when pnuckowski/aioresponses#262 is merged and released
Yep. Would be great to have a fix for it released. If there is a way we can speed it up? |
Because of aio-libs/aiohttp#9866 some tests are failing. This PR can be reverted when pnuckowski/aioresponses#262 is merged and released
Because of aio-libs/aiohttp#9866 some tests are failing. This PR can be reverted when pnuckowski/aioresponses#262 is merged and released
We are going to release a 3.11.1 for backwards compat. https://github.com/aio-libs/aiohttp/actions/runs/11840386977 It would still be good to merge this change though since we don't expect |
3.11.1 is available on PyPI |
changelog: aio-libs/aiohttp@v3.11.0...v3.11.1 no functional changes, release was only to restore compat for testing in pnuckowski/aioresponses#262
Nice. Thanks! @pnuckowski - is the aioresponses library maintained? |
Bump `aiohttp` to `3.11.1` aio-libs/aiohttp#9866 was fixed by pnuckowski/aioresponses#262 (comment) https://pypi.org/project/aiohttp/3.11.1/
Bump `aiohttp` to `3.11.1` aio-libs/aiohttp#9866 was fixed by pnuckowski/aioresponses#262 (comment) https://pypi.org/project/aiohttp/3.11.1/
Thanks, guys! 👍 |
today will upload, first need to fix some issues that occur while uploading to pypi :/ stay tuned |
Yesterday, 3.11 version of `aiohttp` was released with [breaking changes ](https://github.com/aio-libs/aiohttp/releases/tag/v3.11.0 ) which breaks `aioresponses` library used for our mocks and as consequence some of our tests are failing. Ref: pnuckowski/aioresponses#262 Regardless of whether this is fixed in aioresponses, aiohttp can introduce breaking changes in minor versions, so I pin it to the latest tested version as this library is critical for the stability in some of our features. Signed-off-by: Alex <[email protected]>
Ok, thanks a lot, @pnuckowski. :) 🙏 |
Thanks @pnuckowski !
But having it released might make them, to drop it back :) |
Likely won't get dropped until 4.x (if ever) so no need to worry about that. |
released as 0.7.7 |
The underlying issue has been solved: pnuckowski/aioresponses#262
Yesterday, 3.11 version of `aiohttp` was released with [breaking changes ](https://github.com/aio-libs/aiohttp/releases/tag/v3.11.0 ) which breaks `aioresponses` library used for our mocks and as consequence some of our tests are failing. Ref: pnuckowski/aioresponses#262 Regardless of whether this is fixed in aioresponses, aiohttp can introduce breaking changes in minor versions, so I pin it to the latest tested version as this library is critical for the stability in some of our features. Signed-off-by: Alex <[email protected]>
This is still backwards compatible with older versions (tested with 3.10.11 and 3.9.5) as well.