It is imperative that source code passes all the linter checks before this effort is merged.

My attempt to take this for a ride revealed black auto-formats some code that flake8 flags, example of it being

__all__ = (a
   + b 
   + c
   + d )

Flake8 runs on Cython files, and flags legal Cython extensions of Python as syntactic errors.

It is imperative that source code passes all the linter checks before this effort is merged.

My attempt to take this for a ride revealed black auto-formats some code that flake8 flags, example of it being

__all__ = (a
   + b 
   + c
   + d )

Flake8 runs on Cython files, and flags legal Cython extensions of Python as syntactic errors.

The black docs point out to this possibility and provide a flake config option. I have added the exception to the .flake8 file.

@diptorupd I know that muting warnings fixes CI. I would prefer the following way: run checks locally. Find most danger warnings. Fix in separate PRs and the apply this PR.

Fix in separate PRs and the apply this PR.

It will split CI changes from fixes and code improvements.

It will split CI changes from fixes and code improvements.

Yes, #416 has the fixes. I just rebased #416 on top of this PR to see the results. Ultimately, I will merge #416 separately and this PR will have only the code improvement checks here.