END_ASYNC_FOR Python 3.14 backwards jump formatting #177
Conversation
| if isinstance(arg_val, str) | ||
| else repr(arg_val) | ||
| ) | ||
| arg_repr = prefer_double_quote(repr(arg_val)) if isinstance(arg_val, str) else repr(arg_val) |
There was a problem hiding this comment.
I keep seeing gratuitous changes like this. I would be grateful if we could stop with the formatting wars.
I am using black 25.12.0. What is it that causes this formatting?
Is .editorconfig get read in?
There was a problem hiding this comment.
I'm using the Ruff VSCode extension with black 24.10.0. I think the issue is that my formatter's line length was set to a longer value than the default 88 characters, so it was unwrapping lines in the files I was updating.
I'll set it back to 88 so hopefully I can avoid having so much linter noise in future PRs.
There was a problem hiding this comment.
Thanks.
Does adding this pyproject.toml help:
[tool.black]
line-length = 88
If there's something we can do to make things explicit, that'd be good.
I am not opposed to a longer line limit, but I am opposed to formatting wars.
2 participants
This PR makes two changes to
END_ASYNC_FORin Python 3.14:The change to
END_ASYNC_FORis not yet documented indis, but there is an open issue on the CPython github with an associated pull request to update the documentation.