Skip to content

Fix invalid aiohttp import #41

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

Merged
merged 1 commit into from
Mar 16, 2018

Conversation

pfreixes
Copy link
Contributor

A silly bug was introduced because of #29, for an unknown reason the test suit didn't detect that issue.

The web submodule is not automatically imported by aiohttp when we make the typical import aiohttp, we have to import it explicitly.

@haotianw465
Copy link
Contributor

Just want to confirm, did you find this bug when you actually instrumenting aiohttp App? With this fix does tox still pass?

@pfreixes
Copy link
Contributor Author

Yes, raised when I was instrumenting an Aiohttp app with the master branch, more about this discussion here [1], looks like that is intentional so we should fix it.

I've just used pytest for that for the aiohttp tests, and they are passing - as before.

[1] aio-libs/aiohttp#2838

@haotianw465 haotianw465 merged commit f300a86 into aws:master Mar 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants