-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removes 3.13, CPython and PyPy classifiers #198
Comments
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: hugovk/norwegianblue#212
I'd also like to keep the "Implementation" classifiers to make it clear PyPy is supported.
Edit: PR tox-dev/pyproject-fmt-rust#4 will preserve the Implementation classifiers.
The text was updated successfully, but these errors were encountered: