Skip to content

Run black on codebase #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

tony
Copy link

@tony tony commented Jul 6, 2020

See also: Qencode-Corp/qencode-api-python-client#1

Complies with PEP 8 and 257, fixes indentation to 4 spaces.

See also: https://black.readthedocs.io/en/stable/the_black_code_style.html

Complies with PEP 8 and 257, fixes indentation to 4 spaces.

See also: https://black.readthedocs.io/en/stable/the_black_code_style.html
@tony
Copy link
Author

tony commented Jul 6, 2020

As with Qencode-Corp/qencode-api-python-client#1, styling is a matter of opinion

Black has proven to be pretty consistent for me across many codebases with teams and in open source projects. The reason why is code styling however generally is uniform. Early on in python they nailed down 4 space indents. The defaults black has generally look good. Nice editor integrations.

@tony
Copy link
Author

tony commented Jul 11, 2020

Closed in favor of a new PR expanding Python 3 compatibility to the Python 2 package. Qencode-Corp/qencode-api-python-client#6. Includes the fix in this PR

@tony tony closed this Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant