[ENH] Consistent python formatting tool and configuration

[afender]

We should all use the same to avoid lengthy format changes between authors and facilitate reviews.

Initiated by #963 (comment)

[BradReesWork]

@afender this sounds more like a documentation request rather than an feature.enhancement

[BradReesWork]

We are going to follow the boy scout rule (https://www.matheus.ro/2017/12/11/clean-code-boy-scout-rule/) for updating variable names®

[afender]

This is not really related to documentation or variable names.

This is more about the python formatting tool and configuration. In the past, we had PRs auto-editing hundreds of lines (like #963) because we don't have a common formating tool or configuration. So I think we should:

• agree on one like Black that I think Chuck is using too
• have all non-default settings (if any) published on the repo
• run auto formating on all files

[kkraus14]

cuDF uses a combination of Black, flake8, and isort for automatic formatting / linting of Python code. If possible I'd suggest following what cuDF has set up so we can maintain consistent for RAPIDS libraries. We have plans to centralize the configuration but haven't had the spare cycles to do so for now.

[rlratzel]

Another checklist item for this issue should be:

• update CONTRIBUTING.md, like cuDF has done.

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[afender]

Closing after the last release discussion. The reformating problem has not shown up since then and everyone uses black or does the changes manually to comply with flake8.