Closed hugovk closed 4 months ago
Check with https://github.com/tox-dev/pyproject-fmt/releases/tag/2.0.3 for 3.13 we no longer parse tox.ini so you need to do https://pyproject-fmt.readthedocs.io/en/latest/#configuration-file or https://pyproject-fmt.readthedocs.io/en/latest/#pyproject-fmt---max-supported-python in your pre-commit flags.
Thanks, the config file will do.
For this bit of the docs:
https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version
Should we remove that YAML snippet? It doesn't really add anything, we just had an almost identical example YAML in the previous section about pre-commit.
Yes.
Exciting to see the new release! 🎉
I have this in pre-commit:
And
py313
in tox.ini:But pyproject-fmt 2.0.2 is removing the 3.13 Trove classifier:
https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version says it should read the tox config for the upper bound.
For example: https://github.com/hugovk/norwegianblue/pull/212
I'd also like to keep the "Implementation" classifiers to make it clear PyPy is supported.
Edit: PR https://github.com/tox-dev/pyproject-fmt-rust/pull/4 will preserve the Implementation classifiers.