Enable black formatter #152
Conversation
The "setup.py test" is deprecated. We could either run the tests directly by "-m unittest" or simply rely on well established runner "pytest". Let's use the second way here. Signed-off-by: Lukáš Doktor <[email protected]>
"setup.py develop" is deprecated, use pip instead. Signed-off-by: Lukáš Doktor <[email protected]>
the double-curly-brackets do not require escaping and fails in black linter. Signed-off-by: Lukáš Doktor <[email protected]>
address all python black style issues. Signed-off-by: Lukáš Doktor <[email protected]>
to keep the formatting correct add python black to the "make check". As black does not cooperate with autopep on some style options let's expand the default --disable-lint options in our inspektor and rely on black. Signed-off-by: Lukáš Doktor <[email protected]>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
@pevogam this should take care of black ;-) |
Well it's (more-less) their work. Anyway I'll have to get used to the: notation which I do not enjoy... |
Actually this notation is much more flexible when it comes to renames. Just imagine you rename a function changing the number of characters it contains and as a result having to change all follow us tabulation to align it again (something which is also not that simple hard to automate). Now you will only have to change one and the actual line for a rename like this. |
|
Sure, I'm not saying it's bad, it's just something I need to get used to :-) |
2 participants
This PR is built on top of #151 and adds python black style fixes.