davidism, 23 days ago

@brettcannon Have you seen the pyreadiness discussion? https://github.com/di/pyreadiness/issues/18 My thoughts are laid out there.

carlton, 23 days ago

@davidism “strongly prefer not having to update classifiers” — I might get that on a T-shirt 😉

brettcannon, 22 days ago

@carlton @davidism I will admit I am asking this thanks to @hynek and https://github.com/hynek/build-and-inspect-python-package?tab=readme-ov-file#define-python-version-matrix-based-on-package-metadata .It's an interesting way to statically define what versions you want to test against instead of a network call to get the data or some Python package that has the release details which you can never pin (both solutions I have considered). It does shift to wanting a cron job or being very on top of when the new Python versions are released, but that's at least mostly predictable.

carlton, 22 days ago

@brettcannon @davidism @hynek

https://fosstodon.org/@carlton/112167359205161175 😅

henryiii, 23 days ago

@brettcannon This is tricky. Seeing one tells me it's ready for 3.13 and probably tested on it, but not seeing it doesn't tell me it doesn't work. Without the classifier, the next thing I'd check is to see if it has platform specific (or ABI3) wheels that work on 3.13.