This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
[securedrop-proxy] black in dev env and CI #144
Comments
6 tasks
kushaldas
referenced
this issue
Jan 17, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. Now the lint target as the black target as dependency in the Makefile.
kushaldas
referenced
this issue
Jan 20, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster.
kushaldas
referenced
this issue
Jan 20, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
kushaldas
referenced
this issue
Jan 23, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. It has pyproject.toml to mark line length as 100. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
kushaldas
referenced
this issue
Jan 23, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. It also has a flake8 config to mark line legth to 88. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
kushaldas
referenced
this issue
Jan 23, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. It also has a flake8 config to mark line legth to 88. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
kushaldas
referenced
this issue
Jan 23, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. It also has a flake8 config to mark line legth to 88. Now the lint target as the black target as dependency in the Makefile. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
kushaldas
referenced
this issue
Jun 4, 2020
To have latest black, we need updated typed-ast, for that we have to upgrade mypy too, and for mypy upgrade to work, we had to upgrade the mypy-extensions. It first runs isort to check if it passes, and then it runs black. Both uses 100 as line length. setup.py marks Python version as >= 3.7 as we are testing and running the code only on 3.7 on Debian Buster. Also contains the formatting change in proxy.py for black check to run sucessfully on CI.
11 tasks
zenmonkeykstop
changed the title
black in dev env and CI
[securedrop-proxy] black in dev env and CI
Dec 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #55 we ran
black
on the codebase. Let's:black --check
(such that a build fails if black would reformat our code) somewhere in CI before the lint target runs (since if changes are neededmake lint
would reformat the code) - if you have a better idea here feel free to implement itThe text was updated successfully, but these errors were encountered: