formatter

Describe the bug

"EOF in multi-line statement" error is shown to the user as the raw tuple it was returned as, rather than in a nicely formatted message.

To Reproduce

For example:

1. Take this (invalid) file:

print(

2. Run Black on it with no arguments
3. See a message with the EOF error being shown as a raw tuple representation:

error: cannot format test

Very nit-picky, I just happened to have a binary called foo in my path, causing the tests to fail. It might be a good idea to randomize the name when checking for something not found or to use a more lengthy, unlikely-to-be-used name.

--- FAIL: TestRunnerRun (0.28s)
    --- FAIL: TestRunnerRun/#641 (0.01s)
        interp_test.go:2981: wrong output in "alias foo='bar baz'\ntype foo":
 

If the subset of a variable name is "in" inside of the for-loop's for ... in section and requires formatting with a comment around the in-keyword, an invalid output is produced.

For this input:

fn main() {
    for variable_in_here /* ... */ in 0..1 {}
    for variable_in_here in /* ... */ 0..1 {}
    for variable_in_here
    in /* ... */ 0..1 {}
    for variable_in_here
  

This plugin is not GDPR-compliant and the same might be true for other privacy regulations, e.g. the CCPA. I will continue to use the GDPR as an umbrella term for similar regulations.

At the time of this writing, the authors assume that consent is given through the co

We need to update our README.md file before the 1.0 release.