Click 9.0

[Rowlando13]

Theme: reduce overhead and actually fix hacks that we had to make to patch bugs

Tentative Guidelines:

• Deprecate pretty freely as we won't remove deprecations until 10.0.
• make sure to add guidance to the upgrade guide

[ulgens]

Any chance to cut a 8.x release with 3.14 support before this one? It looks like 9.0 will take some time, but 3.14 support is already in place and can be released.

[edgarrmondragon]

Any chance to cut a 8.x release with 3.14 support before this one?

Are there any known issues with 3.14? I've been using 8.3.1 with 3.14 and it seems to be well-supported.

[davidism]

Click has always supported 3.14.

[ulgens]

Are there any known issues with 3.14? I've been using 8.3.1 with 3.14 and it seems to be well-supported.

No issues yet, but also there is no declaration of support. I was checking when 3.14 was added to CI and found that the related commit hasn't been included in a release yet.

Click has always supported 3.14.

I'm not sure what "always" means in this context but I guess you mean it didn't cause any issues yet.

I was planning to use click for another library I'm preparing to release. It will declare support for 3.14, and I was trying to select a min version for click too, by looking for the earliest version that is tested with 3.14. That release doesn't exist yet, and it turns out click doesn't declare support for any Python version at all (no Python minors in the trove classifiers), which I find rather unfortunate from a maintainer's perspective.

If the 8-year-old decision to not manage trove classifiers can be revisited, I'm willing to create a PR to add them.

---

Thanks for the quick response and merry Christmas / happy New Year! 🎄

[Rowlando13]

I don't know much about trove clasifiers other than we don't use them. It seemed like they were not worth the effort at the time. 3.14 has been in the test suite for a few months without any issues.

[ulgens]

It seemed like they were not worth the effort at the time.

Are there any concerns about them? Enabling them only needs a 4-5 lines of string change, and 1 extra line with each update.

3.14 has been in the test suite for a few months without any issues.

Yep. But no release was created after that change in the test suite.

If I were looking at click for a project (not a library), pinning my dependency to the main wouldn't be an issue, but for a library that aims to support 3.14, this is a bit of a deal breaker.

[davidism]

See di/pyreadiness#18 for my reasons not to use python version classifiers.Please drop this line of conversation, it's not changing. Click supports Python 3.14, no pinning to main required. If you find a bug with 3.14, report a bug.