[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/asottile/pyupgrade: v3.15.2 → v3.16.0
• github.com/PyCQA/flake8: 7.0.0 → 7.1.0
• github.com/codespell-project/codespell: v2.2.6 → v2.3.0

[mister-roboto]

@pre-commit-ci[bot] thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

[gforcada]

@davisagli would it be ok to drop pypy3 temporarily? seems that plone/meta needs some fixes/improvements to handle it, but meanwhile, at least GHA would pass.

I'm not sure why test.yml break with plone/meta changes 🤔 I can try to have a look, but as of late seems I don't have much time, so that might not be much of a promise 🫣

[mauritsvanrees]

@davisagli would it be ok to drop pypy3 temporarily? seems that plone/meta needs some fixes/improvements to handle it, but meanwhile, at least GHA would pass.

I think this is fine. From a Plone standpoint, PyPy3 does not need to be supported, as Plone uses C-code (in some Zope packages). But if someone needs it outside of Plone and steps up, we can try to support it again. Maybe a separate GitHub actions file that is not touched at all by plone/meta.

[mauritsvanrees]

I have added a news snippet to say that we currently do not test on PyPy3.

[davisagli]

@mauritsvanrees You also ought to update the trove classifiers in setup.py

[mauritsvanrees]

@davisagli I think it is fine to leave PyPy in the classifiers: we do not drop support, we only no longer test it.

[davisagli]

@mauritsvanrees If we do not test it, then we cannot make any claim that it is supported, in my opinion.

[mauritsvanrees]

@davisagli I have a better idea: restore PyPy3 support in the test setup. :-D. See PR #49.

Apparently the correct way of asking for PyPy3 in actions/setup-python is pypy3.9
The only downside is a slightly weird looking test job "pypypy3.9".