Skip to content
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

Closed
ichard26 opened this issue Jul 17, 2022 · 6 comments · Fixed by #3259
Closed

Upcoming aiohttp 4.0 is breaking our test suite with a new deprecation warning #3176

ichard26 opened this issue Jul 17, 2022 · 6 comments · Fixed by #3259
Labels
C: dependencies C: maintenance Related to project maintenance, e.g. CI, testing, policy changes, releases good first issue Good for newcomers help wanted Extra attention is needed

Comments

@ichard26
Copy link
Collaborator

ichard26 commented Jul 17, 2022

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.

@ichard26 ichard26 added C: dependencies C: maintenance Related to project maintenance, e.g. CI, testing, policy changes, releases labels Jul 17, 2022
@ichard26 ichard26 changed the title aiohttp 4.0 is breaking our test suite with a new deprecation warning Upcoming aiohttp 4.0 is breaking our test suite with a new deprecation warning Jul 17, 2022
@graingert
Copy link
Contributor

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.

Does mypy_primer run the black test suite?

@ichard26
Copy link
Collaborator Author

@graingert There's a PR to make it do so: hauntsaninja/mypy_primer#41

@zsol
Copy link
Collaborator

zsol commented Jul 18, 2022

Nah that mypy primer test should probably do something more trivial than running our test suite. Like maybe running black --check .

@ichard26 ichard26 added help wanted Extra attention is needed good first issue Good for newcomers labels Jul 29, 2022
@shivamdurgbuns
Copy link

So @ichard26 what is required to fix this, I can work on it.

@graingert
Copy link
Contributor

graingert commented Jul 29, 2022

@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

@shivamdurgbuns
Copy link

@graingert Understood! Will do accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: dependencies C: maintenance Related to project maintenance, e.g. CI, testing, policy changes, releases good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
4 participants