Fix Black

[auscompgeek]

Fixes #1909

[auscompgeek]

😕 do we intentionally have invalid Python syntax in that playground file?

cursorless/data/playground/python/values.py

Line 29 in 7369cea

val1 = 0, val2 = 5

The check-ast pre-commit hook complains about it as well, if I add and run it:

check python ast.........................................................Failed
- hook id: check-ast
- exit code: 1

data/playground/python/values.py: failed parsing with CPython 3.11.5:

    Traceback (most recent call last):
      File "~/.cache/pre-commit/repo_yfg8kuk/py_env-python3.11/lib/python3.11/site-packages/pre_commit_hooks/check_ast.py", line 21, in main
        ast.parse(f.read(), filename=filename)
      File "/usr/local/Cellar/[email protected]/3.11.5/Frameworks/Python.framework/Versions/3.11/lib/python3.11/ast.py", line 50, in parse
        return compile(source, filename, mode, flags,
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "data/playground/python/values.py", line 29
        val1 = 0, val2 = 5
        ^^^^^^^^
    SyntaxError: invalid syntax. Maybe you meant '==' or ':=' instead of '='?

[pokey]

I don't think it's necessarily a bad thing to have bad syntax in the playground

[pokey]

Is there not a way to make the exclusion work?

[auscompgeek]

I don't know, it was 1am my time and I just wanted to get black to format my code again

[pokey]

Ok looks like force-exclude was supposed to be a regex. It's strange that there was no error thrown, just silently failing to format any files 🤔

[auscompgeek]

That's… quite amazing. Possibly worth filing an issue, but we should update black first.

[auscompgeek]

Wait, I was running black on the command line wasn't I 😅

[pokey]

Wait, I was running black on the command line wasn't I 😅

yes, appears so, why?