-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Upcoming aiohttp 4.0 is breaking our test suite with a new deprecation warning #3176
Comments
Does mypy_primer run the black test suite? |
@graingert There's a PR to make it do so: hauntsaninja/mypy_primer#41 |
Nah that mypy primer test should probably do something more trivial than running our test suite. Like maybe running |
So @ichard26 what is required to fix this, I can work on it. |
@shivamdurgbuns simplist fix is to append the relevant ignore to filterwarnings https://github.com/psf/black/blob/main/pyproject.toml#L51 You can also use a try/catch to see if the deprecated attribute is still present and then note the mitigation in the filterwarnings comment |
@graingert Understood! Will do accordingly. |
See https://github.com/ichard26/black-deps-ci/runs/7374216061?check_suite_focus=true. We can either bump the lower bound requirement for aiohttp, or we can reuse the approach taken in #2974 for a similar issue. I'll note that aiohttp 4.0 is still under development so breakage will come later, but eventually :)
cc @zsol we should probably configure pytest to not error out on warnings when running under mypy_primer since it'd be pointless busywork and noise for them.
The text was updated successfully, but these errors were encountered: