Skip to content

Conversation

@Mr0grog
Copy link
Member

@Mr0grog Mr0grog commented Dec 20, 2025

Upgrades to the current version of Versioneer. Not really clear whether this supports Python 3.13 and 3.14, but maybe! If so, this should hopefully solve #212.

This is the current version, which as far as I know should be more compatible with current Pythons.
I think this will fail in 3.13 and 3.14 on account of faust-cchardet, but want to test and find out first!
pkg_resources comes from setuptools and is not really a core thing anymore. The right, built-in way to get the same data now is importlib.resources.
@Mr0grog
Copy link
Member Author

Mr0grog commented Dec 20, 2025

It looks like the current errors in 3.13 and 3.14 are coming from Sentry, and we’ll need to upgrade to v2 (also long overdue). Don’t have more time for that tonight, though. Will have to come back to this.

I also removed compatibility with Python 3.9 and earlier here. I think that’s probably OK since they no longer receive even security support (current security support goes back to 3.10 and active support goes back to 3.13). This frees us up to clean up other stuff and drop some extreme legacy stuff.

There's a fair amount that should be cleaned up and revisited here, but this seems to work and still send the right stuff to Sentry for now.
@Mr0grog Mr0grog changed the title Upgrade versioneer to v0.29 Support Python v3.12, 3.13, 3.14 Dec 20, 2025
@Mr0grog
Copy link
Member Author

Mr0grog commented Dec 20, 2025

Everything passes!

@Mr0grog Mr0grog merged commit f675ea8 into main Dec 20, 2025
14 checks passed
@Mr0grog Mr0grog deleted the 212-upgrade-versioneer branch December 20, 2025 14:35
@github-project-automation github-project-automation bot moved this from Inbox to Done in Web Monitoring Dec 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants