This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
Drop resolve attribute #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Min3953 thx! 🎆 |
|
I thought about more smooth transition but if just dropping attr/param is good for you -- I can live with it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aio-libs/aiohttp#2377
resolve attribute was deprecated in aiohttp 1.x. And then, it was drop in aiohttp>=3.0.(aio-libs/aiohttp#2379)
So, if someone use aiohttp>=3.0, this library raise error. Therefore, I drop the resolove attribute.
Aiohttp <3.0 does not cause an error even if the attribute is missing. This is because there is a default asign value.