Skip to content

mypy: fix ci, use a newer flake8 and flake8-pyi, ignore a new error #8812

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
May 13, 2020

Conversation

hauntsaninja
Copy link
Collaborator

The versions are necessary because of some change involving switching from optparse to argparse.

Here are the E741 errors that would be ignored if this was merged.

./mypy/fastparse.py:327:39: E741 ambiguous variable name 'l'
./mypy/fastparse.py:334:35: E741 ambiguous variable name 'l'
./mypy/fastparse.py:1339:35: E741 ambiguous variable name 'l'
./mypy/fastparse.py:1399:39: E741 ambiguous variable name 'l'
./mypy/fastparse2.py:196:35: E741 ambiguous variable name 'l'
./mypy/meet.py:214:13: E741 ambiguous variable name 'l'
./mypy/meet.py:407:20: E741 ambiguous variable name 'l'
./mypy/typeanal.py:1170:13: E741 ambiguous variable name 'l'
./mypy/traverser.py:86:13: E741 ambiguous variable name 'l'
./mypy/report.py:298:46: E741 ambiguous variable name 'l'
./mypy/semanal.py:4524:38: E741 ambiguous variable name 'l'
./mypy/subtypes.py:336:17: E741 ambiguous variable name 'l'
./mypy/subtypes.py:1312:17: E741 ambiguous variable name 'l'
./mypy/test/data.py:383:16: E741 ambiguous variable name 'l'
./mypy/test/data.py:401:32: E741 ambiguous variable name 'l'

Copy link
Member

@emmatyping emmatyping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@emmatyping emmatyping merged commit c90b405 into python:master May 13, 2020
@hauntsaninja hauntsaninja deleted the ci branch May 13, 2020 18:56
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