A PR to document the process of fixing pylint issues with Black, and contribute a few small changes to raise the pylint score from 4.11 to 4.14.
My workflow:
pylint-badge contextualized pylint.svg calculates the current pylint score.
black --check contextualized --target-version=py37 gives a list of files to be updated by black.
Picking a particular filefoo.py from the list above, I run black contextualized/foo.py --target-version=py37. This makes formatting changes to align with the Black style.
Manually inspect the changes with git diff contextualized/foo.py.
Re-run pylint-badge contextualized pyling.svg to re-calculate the pylint score, and re-create a badge with that score. Sanity check that pylint score did not decrease by making style changes with black.
Currently, black also suggests a number of changes to files which are being modified, and close to merging, in other branches. This PR should not include any of those files.
A PR to document the process of fixing pylint issues with Black, and contribute a few small changes to raise the
pylint
score from 4.11 to 4.14.My workflow:
pylint-badge contextualized pylint.svg
calculates the currentpylint
score.black --check contextualized --target-version=py37
gives a list of files to be updated byblack
.foo.py
from the list above, I runblack contextualized/foo.py --target-version=py37
. This makes formatting changes to align with the Black style.git diff contextualized/foo.py
.pylint-badge contextualized pyling.svg
to re-calculate thepylint
score, and re-create a badge with that score. Sanity check thatpylint
score did not decrease by making style changes withblack
.Currently,
black
also suggests a number of changes to files which are being modified, and close to merging, in other branches. This PR should not include any of those files.