Conversation
updates: - [github.com/astral-sh/ruff-pre-commit: v0.9.9 → v0.11.4](astral-sh/ruff-pre-commit@v0.9.9...v0.11.4) - [github.com/pre-commit/mirrors-clang-format: v19.1.7 → v20.1.0](pre-commit/mirrors-clang-format@v19.1.7...v20.1.0) - [github.com/python-jsonschema/check-jsonschema: 0.31.2 → 0.32.1](python-jsonschema/check-jsonschema@0.31.2...0.32.1) - [github.com/woodruffw/zizmor-pre-commit: v1.4.1 → v1.5.2](zizmorcore/zizmor-pre-commit@v1.4.1...v1.5.2) - [github.com/abravalheri/validate-pyproject: v0.23 → v0.24.1](abravalheri/validate-pyproject@v0.23...v0.24.1)
for more information, see https://pre-commit.ci
|
New clang-format gave this error before, removing https://github.com/python-pillow/Pillow/actions/runs/14315399800/job/40120258457?pr=8873 |
|
Investigating, I think clang is detecting some files as C++, and some as C. Looking at https://clang.llvm.org/docs/ClangFormatStyleOptions.html#clang-format-style-options, I think a way to specify both languages would be to list the options twice - radarhere@8b7d724 - but you might think that is unsightly. |
|
If there's no way to force it to check as C, then that's fine by me, we don't need to change it too often. |
|
https://clang.llvm.org/docs/ClangFormatStyleOptions.html#language
So radarhere@05dea18 is another option. |
|
Either fine with me :) |
radarhere
left a comment
There was a problem hiding this comment.
Ok, I've listed the options twice.
updates: