Missing python version classifiers

[skynavga]

Please add python version classifiers to pyproject.toml to document tested compatibility with python versions. For example, is this project compatible with Python 3.13?

[davidism]

I don't plan to add these back. This is a policy across all Pallets projects, and has been discussed before. Copying my comment from a previous issue:

The "3" classifier on its own tells you nothing of the supported versions. So what we get into is asking for us to continually maintain the "3.x" classifiers. But that means that even if there are no changes ready for release, we have to make a new release with a new version number, just to mark the package as "supports 3.10". And that doesn't inform users about the existing versions that cannot be updated to indicate they also support 3.10. And while you've opened the issue on one package, there are 7 main Pallets projects and the Pallets-Eco projects, so it's just requesting more maintainer busy work for no real benefit to us.

See di/pyreadiness#18 for more discussion.

[skynavga]

I would note that

• out of 15 direct, production (non-development) dependencies in the project I am using itsdangerous on, only your package fails to declare Python 3.12 (or any other version) compatibility;
• the effort to add a classifier is trivial (and less effort than responding to requests like mine), independently of whether it is synchronized with a release;
• while "no real benefit to us" may apply to you and your co-maintainers, it does not apply to your customers (us);

I encourage you to reconsider your current policy.

[ThiefMaster]

it does not apply to your customers (us)

I find this argumentation quite rude in case of open source projects that tend to be maintained by people during their free time....

[davidism]

only your package fails to declare

We do declare compatibility, we set requires-python in the packaging metadata.

the effort to add a classifier is trivial

As explained above, it is not.