-
Notifications
You must be signed in to change notification settings - Fork 685
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
Update flake8/pyflakes so it understands new mypy comments #6427
Labels
Comments
lb803
added a commit
to lb803/securedrop
that referenced
this issue
Dec 6, 2022
…er required). Addressing the issue: freedomofpress#6427
lb803
added a commit
to lb803/securedrop
that referenced
this issue
Dec 6, 2022
…er required). Addressing the issue: freedomofpress#6427
lb803
added a commit
to lb803/securedrop
that referenced
this issue
Dec 6, 2022
…er required). Addressing the issue: freedomofpress#6427
lb803
added a commit
to lb803/securedrop
that referenced
this issue
Dec 7, 2022
…er required). Addressing the issue: freedomofpress#6427
10 tasks
cfm
added a commit
that referenced
this issue
Jan 10, 2023
…er required). Addressing the issue: #6427
cfm
pushed a commit
that referenced
this issue
Jan 10, 2023
…er required). Addressing the issue: #6427
(This will be resolved by #6885) |
Indeed, we've dropped flake8/pyflakes entirely with ruff now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a good first issue for new contributors to take on, if you have any questions, please ask on the task or in our Gitter room!
The old version of flake8/pyflakes doesn't understand advanced mypy type comments like
# type: ignore[override]
. This was fixed in PyCQA/pyflakes#455 (pyflakes 2.2.0 I believe).(the second instance is from the unmerged sessions PR)
The text was updated successfully, but these errors were encountered: