allow installing under Python 3.14 and newer #175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've tested
kobodlunder newly released Python 3.14 (3.14.0rc3to be precise, since that's the most recent releasepyenvincludes) and didn't run into any issues with either CLI or web interface.At the moment, users running Python 3.13 (ex. those on current Ubuntu 25.04) and newer that try to install kobodl using
pip/pipxwill be served an old (0.8.0) release - one which uses the no longer functional activation system (unless they bypass the check withpip install --ignore-requires-python kobodl). ex: #174The reason I've opted to remove the upper bound completely is that, without constant maintenance, users will inevitably be forced to install the old version of kobodl whenever a newer Python drops. I do appreciate the fact that this does risk running into potential incompatibility issues down the line, but fixing them if and when they actually do pop up seems like a lesser evil 😄