Fix Formatting Options and VSCode autopep8 Extension#32
Conversation
|
Another inconsistency? Applying autopep8 locally, this is not required. It only happens when running make. Question is why and where is the inconsistency? |
|
There might be a difference where VSCodes' autopep8 and the command run by make source their settings. I would trust the make command one, since it's taking its settings from the |
|
Okay, I've just confirmed in a code space, the autopep8 extension works differently than the |
|
Ah, I think I've found the issue: In pyproject.toml, I set From the VSCode log 2025-10-08 12:27:32.513 [info] CWD Server: /workspaces/evopt
2025-10-08 12:27:32.574 [info] [Trace - 12:27:32 PM] Received notification 'window/logMessage'.
2025-10-08 12:27:32.574 [info] usage: autopep8 [-h] [--version] [-v] [-d] [-i] [--global-config filename]
[--ignore-local-config] [-r] [-j n] [-p n] [-a]
[--experimental] [--exclude globs] [--list-fixes]
[--ignore errors] [--select errors] [--max-line-length n]
[--line-range line line] [--hang-closing] [--exit-code]
[files ...]
--recursive cannot be used with standard input |
|
Now extension, make, and CI should be consistent. |
|
Reading my stupid "Ah" and "Okay" openings, I realize I sound like an LLM and I want to apologize for this. |
|
Stream of consciousness 😂 |
|
Realize I don't unterstand the python philosophy. Why are we using |
recursivesetting frompyproject.tomlto be compatible with autopep8 VSCode extension