-
Notifications
You must be signed in to change notification settings - Fork 94
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
feature: async support #225
Conversation
rewrite tests using pytest-aiohttp
add pytest-aiohttp remove pytest-asyncio remove aiohttp
Codecov Report
@@ Coverage Diff @@
## master #225 +/- ##
==========================================
- Coverage 92.90% 92.34% -0.57%
==========================================
Files 6 6
Lines 2792 2847 +55
==========================================
+ Hits 2594 2629 +35
- Misses 198 218 +20
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Switch "from unittest.mock import patch" to pytest.warns. Maybe it is the reason why aiohttp and python 3.7 does not go together on CI builds, and if it is not a root cause, it looks cleaner anyway. Stick to one testing framework stuff.
…into async-feature
Switch "from unittest.mock import patch" to pytest.warns.
url = url.rstrip('/') + '/' | ||
|
||
if metadata is None: | ||
metadata = await _async_fetch_metadata(connection, url, logger) |
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.
Don't you kill all async here? What's the difference between the regular client?
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.
no, await (asynchronous wait) is calling the asynchronous _async_fetch_metadata function.
This is basically the code from PR #210 (that one merged to feature-branch), by @Albo90, with more tests.
This mess will be squashed to one "feature" commit to master.