Skip to content

[pre-commit.ci] pre-commit autoupdate and Python 3.10 to 3.14 - #397

Merged
cclauss merged 6 commits into
developfrom
pre-commit-ci-update-config
Sep 30, 2025
Merged

[pre-commit.ci] pre-commit autoupdate and Python 3.10 to 3.14#397
cclauss merged 6 commits into
developfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci

@pre-commit-ci pre-commit-ci Bot commented Sep 29, 2025

Copy link
Copy Markdown
Contributor

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.13.1 → v0.13.2](astral-sh/ruff-pre-commit@v0.13.1...v0.13.2)
@cclauss cclauss changed the title [pre-commit.ci] pre-commit autoupdate [pre-commit.ci] pre-commit autoupdate and Python 3.10 to 3.14 Sep 30, 2025
@cclauss
cclauss merged commit b728b3f into develop Sep 30, 2025
14 checks passed
@cclauss
cclauss deleted the pre-commit-ci-update-config branch September 30, 2025 09:22
@aaronliu0130

aaronliu0130 commented Oct 1, 2025

Copy link
Copy Markdown
Member

Since we don't actually rely on any features introduced in 3.10, I would heavily prefer we release with 3.9 support the critical fixes in #376 merged.

@cclauss

cclauss commented Oct 1, 2025

Copy link
Copy Markdown
Member

Python 3.9 goes EoL next week when Python 3.14 is released. Those who refuse to update their codebases from EoL versions can run cpplint via pipx or uvx. This will at least help them to learn the advantages of modern tooling.

@aaronliu0130

Copy link
Copy Markdown
Member

I don't see how dropping an EOL version provides any benefit. It doesn't make cpplint more secure when the user hasn't updated their Python anyway, and the namespace indentation problem was a big regression that I think a lot of projects should have fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants