Autoformatting: PEP8 via black
& blitz .rst
trailing whitespace
#45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #16 and towards the closure of #17, though not closing the latter because here I have provided basic configuration for
flake8
but not went through and addressed all of the errors and warnings it raises, which should be done in another PR since this one is pure (auto-)formatting and I don't want to mix in more significant changes.In this PR I have:
black
andflake8
, using the same config. as cf-python (which I will review shortly in case we want to update it for both libraries);black
on all files in the codebase, via two commits (first for thecfplot
directory for the main codebase, then anything else, mostly docs and setup files etc., by running from the repo root);temp.py
which was in the codebase but shouldn't be, leftover from Andy's files, as evidenced by it failing to be valid Python and supported by the name 'temp';.rst
files that was raised by a nice tool calledsphinx-lint
, which I found because I was hoping to find a library that would allow me to applyblack
to the Python code snippets in the.rst
but found this first and wanted to get rid of the vrey large amount of superfluous whitespace there first. I will investigate for a future PR on a possibleblack
linter for the.rst
Python snippets.